From: "Peter Münster" <pmlists@free.fr>
To: ding@gnus.org
Subject: Re: entering a group is slow
Date: Thu, 19 Jun 2014 23:30:45 +0200 [thread overview]
Message-ID: <874mzg4mey.fsf@micropit.roche-blanche.homenet.org> (raw)
In-Reply-To: <87ionx5aen.fsf@pinto.chemeng.ucl.ac.uk>
On Thu, Jun 19 2014, Eric S Fraga wrote:
> Wow! Mine does not, or not noticeably so. The delay, if any, is
> network latency and the email server, in my case.
Oh, then I would really like to know, where emacs spends the cpu-time on
my system... And why it can become much slower suddenly.
> Sure but if emacs is competing for cpu with anything else, this matters.
Right. But it was not the case on my system. (I use xosview for monitoring
the CPUs: 3 were idle, and the fourth was at 100% because of emacs.)
>> Or perhaps I've done something particular, that has made emacs slow?
>> What could it be...?
>
> What about the summary line? Do you have a highly customised one? In
> my case, the user date function actually contributes non-negligibly to
> the time gnus takes in preparing the summary buffer...
I've tested with the default line, there is no difference.
> otherwise, I am out of ideas and maybe somebody else can jump in!
That would be really appreciated!
Thanks for your efforts,
--
Peter
next prev parent reply other threads:[~2014-06-19 21:30 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
2014-06-19 12:52 ` Eric S Fraga
2014-06-19 21:30 ` Peter Münster [this message]
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=874mzg4mey.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).