From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: <ding@gnus.org>
Subject: Re: entering a group is slow
Date: Thu, 19 Jun 2014 08:41:04 +0100 [thread overview]
Message-ID: <87vbrxs5wv.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87oaxqrkze.fsf@micropit.roche-blanche.homenet.org> ("Peter \=\?utf-8\?Q\?M\=C3\=BCnster\=22's\?\= message of "Wed, 18 Jun 2014 23:00:53 +0200")
On Wednesday, 18 Jun 2014 at 23:00, Peter Münster wrote:
[...]
> 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 !
I am not sure if elp reports cpu time or elapsed (wall clock)
time. Also, remember that my system has 8 cpu cores and large
memory. Bogomips alone is not a full measure of system
capability. What storage system are you using? I.e. do you have a slow
disk? Etc.
> 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?
Are you swapping, by any chance? How much memory does your system have?
Type "free" at the shell.
--
: Eric S Fraga, GnuPG: 0xFFFCF67D
: in Emacs 24.3.1 + Ma Gnus v0.12 + evil evil-git-a6a27e0
: BBDB version 3.0.50 (2013-11-16 11:30:49 -0600)
next prev parent reply other threads:[~2014-06-19 7:41 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
2014-06-19 7:41 ` Eric S Fraga [this message]
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=87vbrxs5wv.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--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).