From: Sascha Silbe <sascha-ml-reply-to-2010-3@silbe.org>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Slow opening of threads?
Date: Fri, 22 Oct 2010 19:19:39 +0200 [thread overview]
Message-ID: <1287766308-sup-224@twin.sascha.silbe.org> (raw)
In-Reply-To: <1287739347-sup-2987@blake>
[-- Attachment #1.1: Type: text/plain, Size: 1196 bytes --]
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 #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-10-22 18:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 9:23 Shadowfirebird
2010-10-22 10:40 ` Amadeusz Żołnowski
2010-10-22 11:48 ` Shadowfirebird
2010-10-22 13:09 ` Moritz Wilhelmy
2010-10-22 18:02 ` Shadowfirebird
2010-10-22 23:32 ` Moritz Wilhelmy
2010-10-22 11:04 ` Gaute Hope
2010-10-22 11:16 ` Philipp Überbacher
2010-10-22 12:21 ` Ben Walton
2010-10-22 12:38 ` Mark Alexander
2010-10-22 13:03 ` Shadowfirebird
2010-10-22 16:28 ` Mark Alexander
2010-10-22 17:19 ` Sascha Silbe [this message]
2010-10-22 19:56 ` Shadowfirebird
2010-10-23 8:28 ` Sascha Silbe
2010-10-23 10:42 ` Shadowfirebird
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1287766308-sup-224@twin.sascha.silbe.org \
--to=sascha-ml-reply-to-2010-3@silbe.org \
--cc=sup-talk@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox