Excerpts from Shadowfirebird's message of Fri Oct 22 11:23:42 +0200 2010: > Is it me, or is Sup sometimes very slow at opening a thread? I mean: a couple of minutes to open a thread with two or three messages and no attachments, about one time in three? My experience is that a) thread opening time is proportional to cumulated message size and b) time for collapsing/expanding a message is proportional to the number of (expanded) lines in the buffer. In both cases there's a large factor involved. Are you getting different timings for the same thread (remember to flush all OS level caches to check this) or are some threads always slow? Does it happen in conjunction with polling? I noticed that sup doesn't always display "Flushing index..." right away (maybe it doesn't flush the output buffer when displaying the message?). FWIW, notmuch is not much faster (SCNR) on my systems. Sup is alternating between IO bound and CPU bound; notmuch kind of eliminates the CPU bound part, but because it doesn't support mbox the IO bound part increases significantly. I imagine that notmuch would benefit greatly from an SSD. Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk