From: "Peter Münster" <pmlists@free.fr>
To: ding@gnus.org
Subject: Re: entering a group is slow
Date: Wed, 18 Jun 2014 23:00:53 +0200 [thread overview]
Message-ID: <87oaxqrkze.fsf@micropit.roche-blanche.homenet.org> (raw)
In-Reply-To: <87wqceuqac.fsf@ucl.ac.uk>
On Wed, Jun 18 2014, Eric S Fraga wrote:
>> gnus-thread-sort-by-most-recent-date 1981 4.8174347399 0.0024318196
>> gnus-thread-latest-date 3962 4.6299316569 0.0011685844
>
> Using your settings, on a system with 4788 bogomips power (x8, mind
> you), if I enter an imap group that has just over 2200 messages, but
> with most of them read, I get the following from elp:
>
> | gnus-thread-sort-by-most-recent-date | 23129 | 1.0279419529 | 4.444...e-05 |
> | gnus-thread-latest-date | 46258 | 0.8665619080 | 1.873...e-05 |
>
> Not sure if this helps you or not...
Yes and no. It helps to explore the problem, but I still don't understand...
Your CPU is about 1.26 times slower than mine, but your
gnus-thread-latest-date is about 62 times faster. That means, that your
gnus-thread-latest-date uses about 80 times less CPU cycles than mine !
Now I've tried with nntp+news.gmane.org:gmane.emacs.gnus.general, to see
if the back-end matters: nntp is worse, even 0.0052218751s per call.
What could be the reason for this slowness?
I've used ELP also with the packages "mail" and "message", but there are
no slow functions...
Further information: All these tests are done with emacs started on
June 8, that means 10 days uptime. Now, I've just restarted emacs and
the time per call is 0.0002029752s. Much better, but still worse than
your result.
Why is gnus-thread-latest-date so slow on my system?
Why does the slowness depend on the emacs-uptime?
TIA for any help,
--
Peter
next prev parent reply other threads:[~2014-06-18 21:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 9:03 Peter Münster
2014-06-13 13:31 ` Igor Sosa Mayor
2014-06-13 14:03 ` Peter Münster
2014-06-17 8:02 ` Peter Münster
2014-06-17 8:48 ` Eric S Fraga
2014-06-17 9:08 ` Peter Münster
2014-06-18 8:10 ` Eric S Fraga
2014-06-18 9:19 ` Peter Münster
2014-06-18 16:38 ` Eric S Fraga
2014-06-18 21:00 ` Peter Münster [this message]
2014-06-19 7:41 ` Eric S Fraga
2014-06-19 9:45 ` Peter Münster
2014-06-19 12:52 ` Eric S Fraga
2014-06-19 21:30 ` Peter Münster
2014-09-08 0:10 ` lee
2014-09-08 7:45 ` Peter Münster
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=87oaxqrkze.fsf@micropit.roche-blanche.homenet.org \
--to=pmlists@free.fr \
--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).