From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Profiling
Date: Wed, 31 Dec 2003 02:39:50 +0100 [thread overview]
Message-ID: <m3ad59rcih.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <ullougah8.fsf@xpediantsolutions.com>
Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
> While it may be more complex to design, its implementation should
> not be too difficult, and the performance should be much better.
> I'll look into it tomorrow.
Cool.
> Any suggestions as to what else may be done? On a long-term
> perspective, should we consider making gnus-newsgroup-unreads a
> sequence rather than a list?
I think this would probably be the way to go in the longer term;
yes. (The same goes for all the article lists -- none of them should
be de/compressed.) However, fixing this is probably a big task.
Or perhaps not -- the places where articles are added to the lists
are actually somewhat containable...
I'd also be worried about performance, but even that is something
that I haven't looked into.
What's faster -- `(memq article gnus-newsgroup-unreads)' or (the
imaginary) `(gnus-member-of-range article gnus-newsgroup-unread-range)'?
It isn't immediately obvious which one of these would win...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2003-12-31 1:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-30 3:58 Profiling Lars Magne Ingebrigtsen
2003-12-30 5:06 ` Profiling Kevin Greiner
2003-12-31 1:39 ` Lars Magne Ingebrigtsen [this message]
2004-01-04 15:37 ` Profiling Per Abrahamsen
2004-01-04 20:41 ` Profiling Lars Magne Ingebrigtsen
2003-12-31 1:49 ` Profiling Michael Cook
2004-01-03 16:56 ` Profiling Robert Marshall
2004-01-01 13:51 ` Spam processing slows down group exit (was: Profiling) Reiner Steib
2004-01-02 16:08 ` Spam processing slows down group exit Ted Zlatanov
2004-01-02 18:40 ` Reiner Steib
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=m3ad59rcih.fsf@quimbies.gnus.org \
--to=larsi@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).