From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: IMAP Performance
Date: 16 Apr 2001 16:40:15 -0400 [thread overview]
Message-ID: <m3r8yso9x6.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <vxkoftx6onu.fsf@cinnamon.vanillaknot.com> (Karl Kleinpaste's message of "16 Apr 2001 07:59:33 -0400")
Karl Kleinpaste <karl@charcoal.com> writes:
> Russ Allbery <rra@stanford.edu> writes:
> > Moving and copying messages is rather slow in nnml too. I'd love to see
> > that fixed. It really shouldn't take hours, or even minutes, to move a
> > few thousand messages between nnml groups if one can use rename() in the
> > underlying file system
nnmaildir uses add-name-to-file and delete-file. Well, sometimes -
nnmaildir-request-move-article binds nnmaildir--file to the article
filename in a (let), puts the message in a buffer, and proceeds to
eval the foorm passed by Gnus. nnmaildir-request-accept-article then
checks nnmaildir--file and tries add-name-to-file before falling back
to copying the buffer. But I think sometimes Gnus arranges things so
that -request-accept-article isn't called until after
-request-move-article returns, so nnmaildir--file no longer holds the
filename. This ought to be solved by fixing the backend interface, I
think.
> Messages can't simply be renamed because e.g. Xref headers must be rebuilt.
nnmaildir generates Xrefs on the fly, so this isn't a problem. At
present, the generates Xrefs are fairly useless, but is fixable.
paul
next prev parent reply other threads:[~2001-04-16 20:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-15 18:22 Johan Parin
2001-04-15 18:44 ` simon
2001-04-15 20:44 ` Russ Allbery
2001-04-16 11:59 ` Karl Kleinpaste
2001-04-16 20:40 ` Paul Jarc [this message]
2001-04-16 22:43 ` Russ Allbery
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=m3r8yso9x6.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
/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;
as well as URLs for NNTP newsgroup(s).