From: nyc4bos@aol.com
To: ding@gnus.org
Subject: Re: Gnus and Gmane speed
Date: Thu, 30 Sep 2010 20:37:52 -0400 [thread overview]
Message-ID: <84y6ai928v.fsf@aol.com> (raw)
In-Reply-To: <m37hi3ci75.fsf@quimbies.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> nyc4bos@aol.com writes:
>
>> Not sure if they are slow or not but my `gnus-summary-line-format' is:
>
> The way to find out is to try it with the default value and see whether
> it makes a difference.
It didn't make a noticable difference (approximately 1 minute).
Out of the 16 minutes it took to see the summary of
gmane.emacs.gnus.general, the following happened:
`SPC' (gnus-group-read-group) started at 7:13PM
Fetching headers for gmane.emacs.gnus.general...
Unknown charset: unknown
Fetching headers for gmane.emacs.gnus.general...done at 7:15PM
Sorting threads...done at 7:19PM
Generating summary...done at 7:29
This was with these settings:
(setq gnus-thread-sort-functions
'((not gnus-thread-sort-by-date))
gnus-article-sort-functions
'((not gnus-article-sort-by-date))
When I removed these settings, "Sorting threads" was pretty quick but
generating "Generating summary" was about the same (approximately
10 minutes).
next prev parent reply other threads:[~2010-10-01 0:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 2:08 nyc4bos
2010-09-30 16:25 ` Lars Magne Ingebrigtsen
2010-10-01 0:37 ` nyc4bos [this message]
2010-10-01 16:53 ` Lars Magne Ingebrigtsen
-- strict thread matches above, loose matches on Subject: below --
2010-09-26 2:10 nyc4bos
2010-09-29 3:37 ` Sivaram Neelakantan
2010-09-29 14:10 ` Lars Magne Ingebrigtsen
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=84y6ai928v.fsf@aol.com \
--to=nyc4bos@aol.com \
--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).