Gnus development mailing list
 help / color / mirror / Atom feed
From: lee <lee@yun.yagibdah.de>
To: ding@gnus.org
Cc: pmlists@free.fr
Subject: Re: entering a group is slow
Date: Mon, 08 Sep 2014 02:10:32 +0200	[thread overview]
Message-ID: <87d2b7dlaf.fsf@yun.yagibdah.de> (raw)
In-Reply-To: <874mzg4mey.fsf@micropit.roche-blanche.homenet.org> ("Peter \=\?utf-8\?Q\?M\=C3\=BCnster\=22's\?\= message of "Thu, 19 Jun 2014 23:30:45 +0200")

Peter Münster <pmlists@free.fr> writes:

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

You might be experiencing some latency from your storage system.  Does
top show a lot of waitstates when you're entering a group, or when disk
activity is going on?


-- 
Knowledge is volatile and fluid.  Software is power.



  reply	other threads:[~2014-09-08  0:10 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
2014-09-08  0:10                           ` lee [this message]
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=87d2b7dlaf.fsf@yun.yagibdah.de \
    --to=lee@yun.yagibdah.de \
    --cc=ding@gnus.org \
    --cc=pmlists@free.fr \
    /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).