Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Checking new mail very slow with current CVS
Date: Wed, 26 Dec 2001 00:11:58 +0100	[thread overview]
Message-ID: <ilupu52ki81.fsf@extundo.com> (raw)
In-Reply-To: <ylvgev6jjr.fsf@windlord.stanford.edu> (Russ Allbery's message of "Tue, 25 Dec 2001 14:07:04 -0800")

Russ Allbery <rra@stanford.edu> writes:

>> M-x elp-instrument-package RET gnus RET (try `mail' and `nn' as well)
>> and post the M-x elp-results RET.
>
> You make this sound so easy.  :)

It is easy.  elp.el under XEmacs was broken.  I've sent a patch.

> Function Name                           Call Count  Elapsed Time  Average Time
> ======================================  ==========  ============  ============
> gnus-group-get-new-news                 1           5.8076979999  5.8076979999
> gnus-get-unread-articles                1           3.6845229999  3.6845229999
> gnus-read-active-file                   1           1.7725740000  1.7725740000

> Function Name                           Call Count  Elapsed Time  Average Time
> ======================================  ==========  ============  ============
> nnml-request-update-info                228         0.9812729999  0.0043038289
> nnml-possibly-change-directory          458         0.7332279998  0.0016009344
> nnml-marks-changed-p                    228         0.4948360000  0.0021703333

Is 5.8 seconds slow?  I guess the new marks stuff makes up for 1
second of that time.  Hm.  But `nnml-request-update-info' takes 0.5
seconds longer than `nnml-marks-changed-p' which should only happen
when Gnus starts the first time (or if some other Gnus changed the
files).  Then the marks stuff should only be bound by the extra time
spent in `nnml-marks-changed-p'.  You could try adding a
'nnml-marks-is-evil' server parameter.

But maybe something else has changed as well that makes things slow.




  parent reply	other threads:[~2001-12-25 23:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-25  6:49 Russ Allbery
2001-12-25 13:36 ` Simon Josefsson
2001-12-25 22:07   ` Russ Allbery
2001-12-25 22:15     ` Russ Allbery
2001-12-25 23:11     ` Simon Josefsson [this message]
2001-12-26  0:41       ` Russ Allbery
2001-12-26 13:56         ` Simon Josefsson
2001-12-26 21:32           ` Russ Allbery
2001-12-26 21:55             ` Simon Josefsson
2001-12-26 23:26             ` Steve Youngs
2002-01-03 18:59             ` Jan Vroonhof
2002-01-03 19:22               ` Simon Josefsson
2002-01-04 13:00                 ` Jan Vroonhof
2002-01-04 15:19                   ` Jan Vroonhof
2002-01-05  6:02                   ` Russ Allbery
2001-12-27 10:04           ` Russ Allbery
2001-12-27 15:33             ` Simon Josefsson
2002-01-09 17:08               ` Sebastian Krause
2002-01-09 17:42                 ` Simon Josefsson

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=ilupu52ki81.fsf@extundo.com \
    --to=jas@extundo.com \
    --cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).