Gnus development mailing list
 help / color / mirror / Atom feed
From: Daniel Pittman <daniel@rimspace.net>
Subject: Re: No Gnus v0.4 / emacs-cvs terribly slowly operating on large nnfolders
Date: Mon, 20 Mar 2006 22:30:19 +1100	[thread overview]
Message-ID: <871wwxz73o.fsf@rimspace.net> (raw)
In-Reply-To: <87u09tjvdk.fsf@denkblock.local>

Elias Oltmanns <oltmanns@uni-bonn.de> writes:

> Daniel Pittman <daniel@rimspace.net> wrote:
>> Elias Oltmanns <oltmanns@uni-bonn.de> writes:
>>
>>> accessing a 25MB nnfolder takes at least twice as much time and
>>> sometimes even up to four times as much when running No Gnus from
>>> within emacs-snapshot (Debian packaged cvs version) than running in
>>> emacs 21.4. The reason I'm reporting this here is that visiting the
>>> file with C-x C-f directly from emacs does not reveal such a
>>> difference in speed. Yet, every operation performed by gnus on this
>>> nnfolder, as entering, reading articles, expiring, etc, challenges my
>>> patience, to say the least. 
>>
>> Well, the best thing to do is probably to profile the operation of
>> visiting a folder, allowing us to see exactly where time is spent.
>
> Here are the profiles. I went about as follows:
> - Start up emacs2[12],
> - load elp.el,
> - M-x set-varialbe RET elp-sort-by-function RET elp-sort-by-average-time RET,
> - start up gnus,
> - M-x elp-instrument-package RET gnus RET,

You probably want to instrument 'nn*' here as well, to catch the
nnfolder, nnml, etc, backend implementation.  Sorry, I should have
mentioned that, since it isn't obvious.

> - enter folder,
> - M-x elp-results.
>
> Note that there are no delays due to disk access as all data had been
> in cache already.

Nothing stands out to me as an obvious candidate, but perhaps someone
more familiar with the code can help out.

     Daniel
-- 
Digital Infrastructure Solutions -- making IT simple, stable and secure
Phone: 0401 155 707	   email: contact@digital-infrastructure.com.au




  reply	other threads:[~2006-03-20 11:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-20  0:23 Elias Oltmanns
2006-03-20  6:02 ` Daniel Pittman
2006-03-20  9:52   ` Elias Oltmanns
2006-03-20 11:30     ` Daniel Pittman [this message]
2006-03-20 15:25       ` Elias Oltmanns
2006-03-20 21:44         ` Romain Francoise
2006-03-20 23:33           ` Elias Oltmanns
2006-03-21 12:29             ` Romain Francoise
2006-03-20 23:36           ` Miles Bader
2006-03-21 12:13             ` Romain Francoise
2006-03-22  1:07           ` James Cloos

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=871wwxz73o.fsf@rimspace.net \
    --to=daniel@rimspace.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;
as well as URLs for NNTP newsgroup(s).