From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: Asynchronous NNTP group data fetching
Date: Mon, 31 Jan 2011 17:16:18 +0100 [thread overview]
Message-ID: <87vd15f3ql.fsf@dod.no> (raw)
In-Reply-To: <87fws9222d.fsf@gnus.org>
>>>>> Lars Ingebrigtsen <larsi@gnus.org>:
> It seems to work in practise, too. I'm reading from eternal-news, Gmane
> and Quimby, and it sure seems faster to me, but it might all be placebo.
I benchmarked it, with one nnimap server, and 5 NNTP servers (two of
which are news.gmane.org, but that shouldn't make a difference...?).
There are 61 active nntp groups on level 3.
This is on an Intel(R) Pentium(R) 4 CPU 3.00GHz, 1.5GB of memory,
running debian testing, and GNU Emacs 23.2.1.
Before git pull:
(benchmark-run 50 (gnus-group-get-new-news))
(49.284682 11 1.154320999999996)
After git pull and rebuild, and a freshly started emacs:
(benchmark-run 50 (gnus-group-get-new-news))
(28.975652 19 1.3127539999999993)
So... it's nearly twice as fast in real time used, but it spends more
time in garbage collection.
next prev parent reply other threads:[~2011-01-31 16:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 3:18 Lars Ingebrigtsen
2011-01-31 16:16 ` Steinar Bang [this message]
2011-02-01 1:21 ` Lars 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=87vd15f3ql.fsf@dod.no \
--to=sb@dod.no \
--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).