From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: ELP results for entering the Gnus list (~10 seconds elapsed time :)
Date: Tue, 29 Jan 2002 00:45:38 -0500 [thread overview]
Message-ID: <2nelk93e2l.fsf@zsh.cs.rochester.edu> (raw)
In-Reply-To: <873d0phqhy.fsf@inanna.rimspace.net> (Daniel Pittman's message of "Tue, 29 Jan 2002 13:13:26 +1100")
Daniel Pittman <daniel@rimspace.net> writes:
> The attached ELP results are for all for 'gnus' and 'nn', entering the
> list folder.
>
> It had one new message, together with the 36 ticked articles, some three
> years old.
>
> ] wc ~/Mail/xemacs.gnus/.overview
> 11308 324899 4232310 /home/daniel/Mail/xemacs.gnus/.overview
> ] wc ~/Mail/xemacs.gnus/.marks
> 1 130 776 /home/daniel/Mail/xemacs.gnus/.marks
>
> This is Gnus "Built at Sun Jan 27 15:07:21 EST 2002" from CVS.
>
> Mobile P2-400, 288MB RAM. The CPU runs at 100% for nine or ten seconds
> when entering the list under these conditions.
>
> Maybe this will help identify some hot spot for this sort of group. :)
[...]
> Function Name Call Count Elapsed Time Average Time
> ====================================================== ========== ============ ============
> gnus-group-read-group 1 9.506698 9.506698
> gnus-summary-read-group 1 9.5063650000 9.5063650000
> gnus-summary-read-group-1 1 9.506333 9.506333
> gnus-select-newsgroup 1 8.6495510000 8.6495510000
> gnus-fetch-headers 1 8.640656 8.640656
> gnus-get-newsgroup-headers-xover 1 7.906612 7.906612
> gnus-retrieve-headers 2 1.459674 0.7298370000
Maybe gnus-nov-parse-line is the culprit, but it is an inline call in
gnus-get-newsgroup-headers-xover. So, could you evaluate
gnus-get-newsgroup-headers-xover, then run elp again?
ShengHuo
next prev parent reply other threads:[~2002-01-29 5:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-29 2:13 Daniel Pittman
2002-01-29 2:39 ` ShengHuo ZHU
2002-01-29 2:48 ` Daniel Pittman
2002-01-29 5:45 ` ShengHuo ZHU [this message]
2002-01-29 7:48 ` Lars Magne Ingebrigtsen
2002-01-29 19:01 ` Simon Josefsson
2002-02-02 22:06 ` Paul Jarc
2002-01-29 8:04 ` Daniel Pittman
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=2nelk93e2l.fsf@zsh.cs.rochester.edu \
--to=zsh@cs.rochester.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).