From: jim@gonzul.net (Jim Cheetham)
Subject: [sup-talk] Slow import of messages
Date: Tue, 14 Jul 2009 09:22:04 +1200 [thread overview]
Message-ID: <f4cc59760907131422p3dd1d429ka9d334e509b992d7@mail.gmail.com> (raw)
In-Reply-To: <20090713091516.GA21214@ikn.schottelius.org>
On Mon, Jul 13, 2009 at 9:15 PM, Nico
Schottelius<nico-sup at schottelius.org> wrote:
> What's your impression? Am I totally wrong or is sup just
> the wrong tool for handling a lot of messages?
No, it's just slow to index for the first time. Unless you receive
1000s of messages per hour, you should be OK ...
-jim
next prev parent reply other threads:[~2009-07-13 21:22 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 [this message]
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=f4cc59760907131422p3dd1d429ka9d334e509b992d7@mail.gmail.com \
--to=jim@gonzul.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