Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: ding@hpc.uh.edu
Subject: Re: nnimap slowness
Date: Sat, 22 Mar 2003 01:54:53 +0100	[thread overview]
Message-ID: <ilu4r5wz0de.fsf@latte.josefsson.org> (raw)
In-Reply-To: <usmtgv158.fsf@boost-consulting.com> (David Abrahams's message of "Fri, 21 Mar 2003 16:51:47 -0500")

David Abrahams <dave@boost-consulting.com> writes:

> I have a fast connection here (10Mb/s cable modem) and my IMAP server
> seems perfectly snappy and responsive when I use other newsreaders,
> but GNUs is just painfully slow, especially when downloading a message
> with a large attachment.  A 1.6MB attachment can take minutes!
>
> Is there anything magical I can do to make this go faster?  I'd even
> settle for the mildly paranormal as long as it speeds things up!

Is it downloading or article rendering that takes time?  See the
troubleshooting section in the manual for how to tell.  If downloading
is slower than in other clients, something is buggy, but viewing large
messages is known to be slow in Gnus since the article is copied
around a few times.

Hm. Zero-copy would be nice, but would probably require some new emacs
primitive.  Like a text overlay to inline one buffer into another.




  reply	other threads:[~2003-03-22  0:54 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-21 21:51 David Abrahams
2003-03-22  0:54 ` Simon Josefsson [this message]
2003-03-22  1:21   ` David Abrahams
2003-03-22  3:51     ` Simon Josefsson
2003-03-22 16:55       ` David Abrahams
2003-03-22 17:12         ` Simon Josefsson
2003-03-22 17:18           ` David Abrahams
2003-03-22 17:52             ` Simon Josefsson
2003-03-22 18:48               ` David Abrahams
2003-03-30 19:20                 ` Simon Josefsson
2003-03-30 22:12                   ` David Abrahams
2003-03-31 12:30                     ` Simon Josefsson
2003-03-31 22:31                       ` David Abrahams
2003-04-01 11:20                         ` Simon Josefsson
2003-03-31  1:13                   ` Krzysztof Jędruczyk
2003-03-31 12:33                     ` Simon Josefsson
2003-03-31 16:51                     ` Lars Magne Ingebrigtsen
2003-03-31 17:18                       ` Lars Magne Ingebrigtsen
2003-03-31 17:25                       ` Simon Josefsson
2003-04-13 13:45                       ` Krzysztof Jędruczyk
2003-04-18 13:50                         ` David Abrahams
2003-04-18 15:16                           ` David Abrahams
2003-04-19 18:34                             ` Kai Großjohann
2003-04-18 15:44                           ` David Abrahams
2003-04-19 18:35                             ` Kai Großjohann
2003-04-20  9:28                               ` David Abrahams
2003-04-18 19:01                           ` A.J. Rossini
2003-04-18 19:19                             ` David Abrahams
2003-04-19  6:28                               ` Steinar Bang
2003-04-19 20:07                               ` Frank Schmitt
2003-03-23  3:20               ` David Abrahams
2003-03-22 18:47         ` Jody Klymak
2003-03-24  9:12           ` Niklas Morberg

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=ilu4r5wz0de.fsf@latte.josefsson.org \
    --to=jas@extundo.com \
    --cc=ding@hpc.uh.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).