From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: Profiling
Date: Sun, 04 Jan 2004 16:37:05 +0100 [thread overview]
Message-ID: <rj8yknybby.fsf@sheridan.dina.kvl.dk> (raw)
In-Reply-To: <m3ad59rcih.fsf@quimbies.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> 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...
I'm not sure it is relevant here, but rewriting some of the simplest
and most commonly used functions in C may be an option. Customize
first became usable fast when Hrvoje reimplemented widget-get in C.
Basically, calling build-in functions is way faster than calling Emacs
Lisp functions.
I'm pretty sure RMS would accept including a C implementation of
gnus-member-of-range if it gave a significant performance boost.
Of course, you need to be sure the interface is not going to change
more, before doing that.
next prev parent reply other threads:[~2004-01-04 15:37 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 ` Profiling Lars Magne Ingebrigtsen
2004-01-04 15:37 ` Per Abrahamsen [this message]
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=rj8yknybby.fsf@sheridan.dina.kvl.dk \
--to=abraham@dina.kvl.dk \
/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).