From: michael+sup@stapelberg.de (Michael Stapelberg)
Subject: [sup-talk] Slow import of messages
Date: Mon, 13 Jul 2009 11:26:14 +0200 [thread overview]
Message-ID: <1247477044-sup-6433@midna> (raw)
In-Reply-To: <20090713091516.GA21214@ikn.schottelius.org>
Hi Nico,
Excerpts from Nico Schottelius's message of Mo Jul 13 11:15:16 +0200 2009:
> I'm looking at sup as a replacement for mutt.
> Following the idea of sup, I took a snapshot of
> my Mails from 2008-2009 (~56k mails) and run
I have about 33k emails on my IMAP server in my LAN.
> Now the problem is that sup gets about 3 mails per
> second into its index. That means it takes about
I got around 10 MB/s performance using sup-sync. Maybe
your mails are all very large, I don?t know. Maybe maildir is
just a lot slower than IMAP in sup-sync.
> What's your impression? Am I totally wrong or is sup just
> the wrong tool for handling a lot of messages?
My impression is that sup-sync can definitely be improved regarding
its speed. I?m not sure if it is actually doable or if it is some ruby
library (Ferret?) which is the limiting factor here. However, it was
not as bad for me as it is for you ;-).
Best regards,
Michael
next prev parent reply other threads:[~2009-07-13 9:26 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 [this message]
2009-07-13 21:22 ` Jim Cheetham
2009-07-28 19:10 ` 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=1247477044-sup-6433@midna \
--to=michael+sup@stapelberg.de \
/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