From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: nnimap issues
Date: Tue, 28 Sep 2010 15:00:25 +0200 [thread overview]
Message-ID: <yb08w2mvx92.fsf@dod.no> (raw)
In-Reply-To: <m2aan2w9i9.fsf@randomsample.de>
>>>>> David Engster <deng@randomsample.de>:
>> But `g' do feel a lot snappier.
>> I still have the pre-nnimap version of gnus around. Is there a way to
>> objectively time the `g'? (Ie. using elisp, not manual use of wall
>> clock...)
> I've used
> (benchmark-run 50
> (gnus-group-get-new-news))
> to run it 50 times. This will return (total-time number-of-GCs time-for-GCs).
Here are my results, both done on emacs 22.3 on RHEL4, Intel(R) Xeon(TM)
CPU 3.00GHz:
; New gnus
(benchmark-run 50
(gnus-group-get-new-news))
(36.122966999999996 21 1.2593269999999976)
; old gnus
(benchmark-run 50
(gnus-group-get-new-news))
(85.283236 67 3.129354)
So a bit more than twice the wall clock time. This is with a single
IMAP server, and 3 agentized NNTP server, and one un-agentized NNTP
server. No local mail folders.
The "old gnus" test was done on a freshly gnus in a freshly started
emacs, so that should perhaps favour it a bit wrt. GC...? Still, it had
over three times the number of GCs run.
next prev parent reply other threads:[~2010-09-28 13:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-26 10:55 Simon Josefsson
2010-09-26 16:17 ` Lars Magne Ingebrigtsen
2010-09-26 17:08 ` Lars Magne Ingebrigtsen
2010-09-26 18:33 ` Steinar Bang
2010-09-26 18:40 ` Lars Magne Ingebrigtsen
2010-09-26 23:44 ` Daniel Pittman
2010-09-26 17:49 ` Lars Magne Ingebrigtsen
2010-09-27 14:26 ` Simon Josefsson
2010-09-27 16:56 ` Lars Magne Ingebrigtsen
2010-09-27 14:39 ` Simon Josefsson
2010-09-27 17:20 ` Lars Magne Ingebrigtsen
2010-09-27 17:25 ` Steinar Bang
2010-09-27 17:39 ` Julien Danjou
2010-09-27 21:17 ` Frank Schmitt
2010-09-28 8:08 ` Steinar Bang
2010-09-28 8:35 ` David Engster
2010-09-28 13:00 ` Steinar Bang [this message]
2010-09-29 15:06 ` Lars Magne Ingebrigtsen
2010-10-12 6:45 ` Steinar Bang
2010-10-12 12:44 ` 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=yb08w2mvx92.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).