From: David Abrahams <dave@boost-consulting.com>
Subject: Re: nnimap slowness
Date: Sat, 22 Mar 2003 12:18:17 -0500 [thread overview]
Message-ID: <u7kars4km.fsf@boost-consulting.com> (raw)
In-Reply-To: <iluwuirwcjp.fsf@latte.josefsson.org> (Simon Josefsson's message of "Sat, 22 Mar 2003 18:12:26 +0100")
[-- Attachment #1: Type: text/plain, Size: 1585 bytes --]
Simon Josefsson <jas@extundo.com> writes:
> David Abrahams <dave@boost-consulting.com> writes:
>
>>> (but it is most likely MIME decoding and displaying that
>>> takes time, see below).
>>>
>>>>> If downloading is slower than in other clients, something is buggy,
>>>>
>>>> It sure seems like downloading is the problem; the attachment isn't
>>>> displayed except as a MIME button.
>>>
>>> Ah, but the message is still copied around. Collapsing it into a
>>> button is only done at the final moment of display. Yes, this is
>>> inefficient. Nobody has worked on fixing this yet though...
>>
>> Seriously? It only takes a fraction of a second to copy 1.6M on this
>> machine.
>
> Between buffers inside emacs?
I don't know about that.
>> When I look at the status line and see
>>
>> imap read: 774K
>>
>> with the numbers spinning upwards at a rate of only about 15K per
>> second I grow highly doubtful that it's doing anything other than
>> reading data from my IMAP server.
>
> Hm, yes, this sounds as if it is the downloading that takes time. Hm,
> maybe it is due to subprocesses in emacs under Windows. Please try
> profiling the imap and nnimap packages to see where it is spending the
> time. Maybe the gnus package too, so that the total time is available
> too (display probably still takes some non-negligible time).
Here's the result for a `M-G' which is not retrieving any messages at
all, since none were sent (but still does the slow "imap read: ..."
dance up to about 24K). If you want more data, I'll send myself
something big and profile that.
[-- Attachment #2: profile.zip --]
[-- Type: application/zip, Size: 3559 bytes --]
[-- Attachment #3: Type: text/plain, Size: 62 bytes --]
--
Dave Abrahams
Boost Consulting
www.boost-consulting.com
next prev parent reply other threads:[~2003-03-22 17:18 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
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 [this message]
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=u7kars4km.fsf@boost-consulting.com \
--to=dave@boost-consulting.com \
/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).