From: asjo@koldfront.dk (Adam Sjøgren)
Subject: Re: Gnus slow?
Date: Thu, 11 Nov 2004 08:16:23 +0100 [thread overview]
Message-ID: <871xf0yhx4.fsf@koldfront.dk> (raw)
In-Reply-To: <b9ylld9ub00.fsf@jpl.org>
On Wed, 10 Nov 2004 21:47:11 +0900, Katsumi wrote:
> Hi, First of all, I don't have any difficulty in using Gnus. Today
> I'm using both No Gnus v0.2 and latest Gnus CVS for a while, but I
> was not able to find out a remarkable difference of speed between
> them so far. However, a friend of mine wrote to me that the recent
> Gnus is much slower than No Gnus v0.2 for fetching mails. IIRC, I
> also have heard similar utterances by several people in groups and
> mailing lists.
I don't know when this started, it may not be related at all, but I'll
mention it just in case:
Recently I got annoyed by hearing my harddisk make a lot of noise
every time I pressed 'g' in Gnus - when checking for new news on the
three news-servers I use - so I tried strace'ing XEmacs/Gnus.
(I was expecting it to be rather silent when checking news-servers
over the net...)
Gnus was trying to opening a lot of files every time I pressed 'g' -
from the names I gathered that it could be something to do with the
Agent (.agentview?), so I went to the server-buffer and unagentized
everything. (I don't use any functionality of the Agent, that I know
of, but back when it became on by default I didn't turn it off).
That change has made the harddisk-noise while checking for new news go
away. Now I only hear noise when mail is being split and stored, and
after that none of the previous 'hitting the harddisk' occurs.
I don't know if this is significant, to be expected, or something else
entirely, but there you go.
This observation is based on a the cvs-gnus I'm posting this article
with, last updated, uh, this summer; No Gnus v0.3, XEmacs 21.4 (patch
15).
I should probably update.
Best regards,
Adam
--
"More than anything, I won't try" Adam Sjøgren
asjo@koldfront.dk
prev parent reply other threads:[~2004-11-11 7:16 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-10 12:47 Katsumi Yamaoka
2004-11-10 13:05 ` Romain Francoise
2004-11-10 14:39 ` Gabor Z.Papp
2004-11-10 18:41 ` Jesper Harder
2004-11-10 23:40 ` Katsumi Yamaoka
2004-11-11 11:47 ` Romain Francoise
2004-11-12 7:27 ` Katsumi Yamaoka
2004-11-12 8:20 ` Romain Francoise
2004-11-12 9:06 ` Katsumi Yamaoka
2004-11-12 13:15 ` Katsumi Yamaoka
2004-11-12 13:53 ` Romain Francoise
2004-11-15 5:32 ` Katsumi Yamaoka
2004-11-15 13:26 ` Romain Francoise
2004-11-15 16:40 ` Dan Christensen
2004-11-16 16:17 ` Reiner Steib
2004-11-16 20:41 ` Dan Christensen
2004-11-16 21:21 ` Romain Francoise
2004-11-16 21:51 ` Simon Josefsson
2004-11-17 15:22 ` Frank Schmitt
2004-11-17 19:57 ` Romain Francoise
2004-11-18 11:04 ` Frank Schmitt
2004-11-19 7:28 ` Romain Francoise
2004-11-19 14:17 ` Kai Grossjohann
2004-11-19 22:14 ` Frank Schmitt
2004-11-20 16:49 ` Kai Grossjohann
2004-11-20 20:39 ` nnimap syncing (was: Gnus slow?) Steven E. Harris
2004-11-20 22:58 ` nnimap syncing Simon Josefsson
2004-11-22 0:59 ` Gnus slow? Katsumi Yamaoka
2004-11-22 7:57 ` Matt Armstrong
2004-11-22 8:58 ` Kai Grossjohann
2004-11-23 20:43 ` Romain Francoise
2004-11-25 0:19 ` Katsumi Yamaoka
2004-11-25 7:41 ` Romain Francoise
2004-11-25 7:55 ` Katsumi Yamaoka
2004-11-11 7:16 ` Adam Sjøgren [this message]
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=871xf0yhx4.fsf@koldfront.dk \
--to=asjo@koldfront.dk \
/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).