From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Agent gone mad?
Date: Mon, 21 Oct 2002 08:42:26 +0200 [thread overview]
Message-ID: <84bs5os371.fsf@crybaby.cs.uni-dortmund.de> (raw)
In-Reply-To: <878z0slk92.fsf@enberg.org> (Henrik Enberg's message of "Mon, 21 Oct 2002 02:15:53 +0200")
Henrik Enberg <henrik@enberg.org> writes:
> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
>
>> Anyhow, I've now changed gnus-agent.el so that it doesn't try to
>> fetch nonexisting articles anymore. This speeds up my session fetch
>> a lot.
>
> Yup, it sees to be as fast as it used to be.
>
>> is Gnus behaving better now with the change I just made? How bad is
>> it still?
>
> Unusably bad. Everytime I do 'J s', It'll download about 100 megs.
Hm. So it is as fast as before, which is unusably bad :-)
Okay. What's in the 100 megs that it is still downloading? Is it
headers or articles or both? I might need to meditate a lot more
about that code...
Btw, I've now reinstated another change of mine which abstains from
fetching already-fetched messages. Maybe that helps some more.
kai
--
~/.signature is: umop ap!sdn (Frank Nobis)
next prev parent reply other threads:[~2002-10-21 6:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-19 20:55 Henrik Enberg
2002-10-19 21:01 ` Henrik Enberg
2002-10-20 16:35 ` Kai Großjohann
2002-10-21 0:12 ` Henrik Enberg
2002-10-20 19:42 ` Kai Großjohann
2002-10-21 0:15 ` Henrik Enberg
2002-10-21 6:42 ` Kai Großjohann [this message]
2002-10-21 17:42 ` Henrik Enberg
2002-10-21 19:12 ` Kai Großjohann
2002-10-21 19:32 ` Henrik Enberg
2002-10-22 5:50 ` Kai Großjohann
2002-10-22 19:10 ` Henrik Enberg
2002-10-22 20:07 ` Kai Großjohann
2002-10-22 20:37 ` Henrik Enberg
2002-10-23 6:11 ` Kai Großjohann
2002-10-22 9:48 ` Simon Josefsson
2002-10-22 10:02 ` Kai Großjohann
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=84bs5os371.fsf@crybaby.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--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).