From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Further `g' tweaks
Date: Thu, 23 Sep 2010 17:55:53 +0200 [thread overview]
Message-ID: <m3iq1wxxme.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <m24odgri8s.fsf@randomsample.de>
David Engster <deng@randomsample.de> writes:
> Whatever you have done, it's pretty good. I repeated by benchmark-run of
> calling 50 times `gnus-group-get-new-news'. The new code now takes
> ~12.8secs, while the old code takes ~15secs with my setup (one IMAP
> server, 15 groups checked with lots of mail in them).
12 secs? That's way too long, I think. :-)
What does the *gnus trace* buffer look like on a single `g'?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2010-09-23 15:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 22:06 Lars Magne Ingebrigtsen
2010-09-22 22:27 ` Lars Magne Ingebrigtsen
2010-09-22 23:18 ` Dan Christensen
2010-09-23 0:36 ` Dan Christensen
2010-09-23 15:55 ` Lars Magne Ingebrigtsen
2010-09-23 18:31 ` Dan Christensen
2010-09-23 18:39 ` Lars Magne Ingebrigtsen
2010-09-23 8:12 ` David Engster
2010-09-23 15:55 ` Lars Magne Ingebrigtsen [this message]
2010-09-23 17:25 ` David Engster
2010-09-23 17:29 ` 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=m3iq1wxxme.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--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).