Hello Timo!
Any ideas why it may take so long time to open big mbox files with indexes and delivered through dovecot deliver?
So it looks like that something is wrong with the indexes or the algorithm.
For details have a look below.
BTW: procmail filtering through deliver works well now for me in production environment. I'll make some code cleanups and configuration options. Maybe I can release the patch today.
Ciao, Gerhard
On Mon, 3 Jul 2006, Timo Sirainen wrote:
On Jul 3, 2006, at 11:07 PM, Gerhard Wiesinger wrote:
As far as I saw dovecot's deliver process updates some header fields and the index files: Status: X-Keywords: (with a lot of spaces, why?) Content-Length: 6
The extra spaces are there so that if Dovecot needs to update some headers it can take the needed space from there so it doesn't have to move the whole mbox.
Yes, I saw it after I wrote the mail ...
After access with dovecot the following header fields change: Status: O X-IMAPbase: 115195111 0000000009 X-UID: 2
So basically this isn't an advantage over the procmail or any other delivering process top mbox. The problem is that after the first access the X-UID and X-IMAPbase header must be added, so on large mbox files this might take a long time.
Well, first of all Dovecot should take the space it needs from the X-Keywords spaces, so it doesn't need to write all that much data.
Second, the X-UID etc. headers are added by deliver if the mbox file is fully synced against the indexes. So after you had opened it once with IMAP, after that deliver should write the X-UID headers also as long as you don't use something else than Dovecot to modify the mbox.
Ok, that worked well. I tried to deliver some large mails (~50MB) which worked well. After sending around 500MB (10 Mails) I opened the mailbox with pine over imap. It still took a lot of time (>20s) to open the mbox. Indexes should be up2date, so why does it take so long time?
After opening a second time everything is fine.
Any ideas?
Ciao, Gerhard