From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: Gnus slow?
Date: Fri, 12 Nov 2004 18:06:22 +0900 [thread overview]
Message-ID: <b9ysm7fl9m9.fsf@jpl.org> (raw)
In-Reply-To: <87u0rv8on2.fsf@orebokech.com>
You might not need to perform ELP again.
>>>>> In <87u0rv8on2.fsf@orebokech.com> Romain Francoise wrote:
>> I don't know why gnus-activate-group spends so many time and
>> seems to be called twice in B, but it is dominant.
It seems to be caused by calling nntp-request-group by way of
gnus-request-group. It should have been clear if I looked at
the nntp profile which you got. Probably, we should clarify the
reason why it is called frequently.
> It is slow because in version B, Gnus issues GROUP commands to the NNTP
> server and it is synchronous so it has to wait for the answer from the
> server. To make it worse, it does it twice since groups are activated
> twice.
> You will find captures of the NNTP conversation between Gnus and
> news.gmane.org here: <URL: http://orebokech.com/tmp/gnus/>. Version A
> issues LIST ACTIVE commands only, asynchronously. Version B first
> issues GROUP commands for each of my groups, synchronously, then issues
> LIST ACTIVE commands like version A, then does GROUP commands again. I
> see two separate issues:
> - why does version B send GROUP commands where version A doesn't? They
> seem unnecessary.
> - even so, why does version B send them twice?
I saw those captures. Thanks.
next prev parent reply other threads:[~2004-11-12 9:06 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 [this message]
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
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=b9ysm7fl9m9.fsf@jpl.org \
--to=yamaoka@jpl.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).