On Mon, Sep 08, 2014 at 07:25:07PM +0200, Michal Sojka wrote: > after moving my maildirs from SSD to rotating disk it takes mbsync very > long time (several hours) to load a maildir (mbsync prints "Loading > slave..." message). The maildir in question has about 800000 messages. I > looked what takes so long and found that mbsync opens every message to > search for X-TUID header in it (see the end of maildir_scan() function). > > I have two questions: > - What is X-TUID good for? > - Is it possible to disable opening every message and searching for > X-TUID? > these are "temporary UIDs", and mbsync uses them to "bridge an atomicity gap" when storing messages. it queries them only if it finds that it doesn't have all proper UIDs, which means that the previous run (which pulled messages, in your case) didn't terminate cleanly (you should see .journal files in the state dir(s)). if that happens after a clean run, there is something wrong.
i find it weird *how* slow this is for you. the number only makes sense if there are 1-2 seeks for every single file, which would imply that no read-ahead whatsoever takes place ... which would be just weird. how much ram does the machine have? what file system? ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce. Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ isync-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/isync-devel
