Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: nico-sup@schottelius.org (Nico Schottelius)
Subject: [sup-talk] Slow import of messages
Date: Mon, 13 Jul 2009 11:15:16 +0200	[thread overview]
Message-ID: <20090713091516.GA21214@ikn.schottelius.org> (raw)

Hello!

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

   sup-sync --all-sources

Now the problem is that sup gets about 3 mails per
second into its index. That means it takes about

	56k/3 ~= 15k; 15000/60 = 250 minutes

That import is already from a local Maildir (synced with
offlineimap).

For me, this is incredibly slow. Using mutt it's way faster,
not even comparing the fact the speed improvement you get
when dividing into folders.

What's your impression? Am I totally wrong or is sup just
the wrong tool for handling a lot of messages?

Sincerly,

Nico


             reply	other threads:[~2009-07-13  9:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-13  9:15 Nico Schottelius [this message]
2009-07-13  9:26 ` Michael Stapelberg
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=20090713091516.GA21214@ikn.schottelius.org \
    --to=nico-sup@schottelius.org \
    /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