Gnus development mailing list
 help / color / mirror / Atom feed
From: "Peter Münster" <pmlists@free.fr>
To: ding@gnus.org
Subject: Re: entering a group is slow
Date: Thu, 19 Jun 2014 11:45:19 +0200	[thread overview]
Message-ID: <874mzhs05s.fsf@micropit.roche-blanche.homenet.org> (raw)
In-Reply-To: <87vbrxs5wv.fsf@ucl.ac.uk>

On Thu, Jun 19 2014, Eric S Fraga wrote:

> On Wednesday, 18 Jun 2014 at 23:00, Peter Münster wrote:
>
> I am not sure if elp reports cpu time or elapsed (wall clock)
> time.

I guess elapsed time. But it doesn't matter, because when I do the test,
emacs uses 100% CPU time.


> Also, remember that my system has 8 cpu cores and large memory.

But emacs can only use one core.


> 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.

When I do the test, everything is in memory, no disk reading involved.
I have 4GB memory, and the swap area is almost never needed.

You are right, bogomips is perhaps not the only parameter for speed.
Perhaps the CPU cache is also important here.

The speed is acceptable now, with gnus-large-newsgroup = 500, but it
would be interesting to know, why emacs becomes slower after some days
of uptime... ?
Or perhaps I've done something particular, that has made emacs slow?
What could it be...?

-- 
           Peter




  reply	other threads:[~2014-06-19  9:45 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
2014-06-19  9:45                     ` Peter Münster [this message]
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=874mzhs05s.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).