On Tue, Mar 18, 2014 at 06:45:39PM +0200, Ciprian Dorin Craciun wrote: > What is strange is that an initial synchronization works until the > connection drops (the largest number was 70 k emails fetched). > However on a second try the CPU usage happens, just after both stores > have been "selected" (i.e. after it receives all the flags from GMail > for all the emails). > > I must note that the previous version (1.0.4) didn't have this issue. > weird - the exact opposite should be the case (see commit 6d49c343f). :}
though i just remembered that an issue was fixed just recently in the qt code i borrowed from, so see commit dec5f73f5. if that doesn't solve the problem, please run the thing through valgrind --tool callgrind (make sure you have a debug build of mbsync). let it run until you have the feeling that the time spent hanging was sufficient relative to the other time (everything cpu-bound will be incredibly slow, as usually with valgrind). then try to make sense of the log with kcachegrind, or just send it to me. you can also send me the output of adding -D to the mbsync command line. make sure the compressed size is at most in the single-digit megabytes - otherwise please cut out the too repetetive parts. ^^ ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
