From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Using DTrace to profile sup-sync
Date: Sat, 15 Dec 2007 11:38:43 -0800 [thread overview]
Message-ID: <1197747488-sup-7714@south> (raw)
In-Reply-To: <1197745662-sup-1441@south>
Oh, the other difference between what sup-sync does and what Mutt does
is that sup-sync downloads the entire content of the message, parses it
for text regions, and stores those in the Ferret index. That's
significantly more work than just downloading the headers, though I
don't know how much that accounts for the difference in speed.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2007-12-15 19:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-15 15:05 Jjgod Jiang
2007-12-15 19:25 ` William Morgan
2007-12-15 19:38 ` William Morgan [this message]
2007-12-15 21:04 ` William Morgan
2007-12-19 4:38 ` William Morgan
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=1197747488-sup-7714@south \
--to=wmorgan-sup@masanjin.net \
/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