From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] message add speedup
Date: Sun, 26 Apr 2009 17:07:36 -0700 [thread overview]
Message-ID: <1240790767-sup-9896@entry> (raw)
I've merged a branch 'scanning-speedup' into next that doubles the speed
of adding messages to the index. There was a lot of time wasted in
parsing the email headers, which I fixed, and I tweaked a couple other
things. Various other operations that load data from the message source,
like viewing a message thread, should now be slightly faster.
I'm able to index around 70 messages/s on my home computer, which is
still slow, but hey, twice as fast as 35. Time is split about 50/50
between scanning/parsing and Ferret index writing. Sadly, Ruby has a
GIL, so I don't think threading these two operations will buy very much.
(Though there might be complicated ways of getting around that.)
--
William <wmorgan-sup at masanjin.net>
reply other threads:[~2009-04-27 0:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1240790767-sup-9896@entry \
--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