From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: FIXED: Gnus 5.10.6 slow getting new news
Date: Wed, 21 Jan 2004 23:03:30 -0500 [thread overview]
Message-ID: <uektshbot.fsf_-_@xpediantsolutions.com> (raw)
In-Reply-To: <uad4kioxa.fsf@xpediantsolutions.com>
Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
> kspost@news.ti.com writes:
>
>> I upgraded from gnus 5.10.2 to 5.10.6. It is noticeably slower when I
>> press `g' to get new news. It takes about 4 seconds for 5.10.2 and
>> about 20 seconds for 5.10.6. Running strace on the emacs process when
>> I press g shows it running a stat on the .agentview file in all of the
>> newsgroup directories. For example, here is some of the stat lines:
>>
>> lstat64("/home/keith/News/agent/nntp/news.ti.com/uk/tech/digital-tv/crypt/.agentview",0xbfffe380) = -1 ENOENT (No such file or directory)
>> lstat64("/home/keith/News/agent/nntp/news.ti.com/linux/debian/devel/.agentview",0xbfffe380) = -1 ENOENT (No such file or directory)
>> lstat64("/home/keith/News/agent/nntp/news.ti.com/microsoft/public/jp/officexp/word/.agentview",0xbfffdde0) = -1 ENOENT (No such file or directory)
>>
>> I don't see the same stat lines with 5.10.2. Has anyone else seen this?
>
> Keith,
> This is a known issue. I'm testing the patch right now. I should be
> releasing it soon.
The patch has been checked in.
Kevin
next prev parent reply other threads:[~2004-01-22 4:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-17 19:59 kspost
2004-01-19 3:43 ` Kevin Greiner
2004-01-22 4:03 ` Kevin Greiner [this message]
2004-01-22 7:10 ` FIXED: " Andreas Jaeger
2004-02-23 19:20 ` Sebastian D.B. Krause
2004-02-25 18:09 ` Simon Josefsson
2004-02-25 19:01 ` Sebastian D.B. Krause
2004-03-28 23:00 ` v5-10 branch created (was: FIXED: Gnus 5.10.6 slow getting new news) Sebastian D.B. Krause
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=uektshbot.fsf_-_@xpediantsolutions.com \
--to=kgreiner@xpediantsolutions.com \
/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).