From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Slow import of messages
Date: Tue, 28 Jul 2009 12:10:57 -0700 [thread overview]
Message-ID: <1248808053-sup-5358@masanjin.net> (raw)
In-Reply-To: <20090713091516.GA21214@ikn.schottelius.org>
Hi Nico,
Reformatted excerpts from Nico Schottelius's message of 2009-07-13:
> Now the problem is that sup gets about 3 mails per second into its
> index.
As others have pointed out, messages only have to be indexed once, so
this isn't ultimately that big of a deal. But 3m/s seems very slow for a
Maildir source.
With my mbox on my reasonably-fast laptop, I start with around 50m/s
using Ferret, and at 80m/s using Xapian. (These numbers degrade slightly
as the index gets fuller.) I would expect similar numbers from Maildir.
So something weird is happening for you. Do you have a notion of whether
it's disk or CPU that's the bottleneck?
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2009-07-28 19:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 9:15 Nico Schottelius
2009-07-13 9:26 ` Michael Stapelberg
2009-07-13 21:22 ` Jim Cheetham
2009-07-28 19:10 ` William Morgan [this message]
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=1248808053-sup-5358@masanjin.net \
--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