From: Jesper Harder <harder@ifa.au.dk>
Subject: Re: Benchmarking Gnus
Date: Sat, 19 Jan 2002 00:42:26 +0100 [thread overview]
Message-ID: <m38zavw7j1.fsf@defun.localdomain> (raw)
In-Reply-To: <m3d70bavsa.fsf@quimbies.gnus.org> (larsi@gnus.org's message of "Wed, 16 Jan 2002 02:14:07 +0000 (UTC)")
[-- Attachment #1: Type: text/plain, Size: 696 bytes --]
larsi@gnus.org (Lars Magne Ingebrigtsen) writes:
> There are now three things that take about the same time when entering
> a group, and account for 95% of the time spent:
>
> 1) parsing NOV headers (this has gotten slower due to MIME stuff, I'm
> guessing)
> 2) scoring
> 3) creating and outputting the threads
>
> If someone wants to look closer at this, then I'm all for it. :-)
Here's a small tweak, which speeds up threading a bit (around 5-10%):
`gnus-parent-id' is usually called without the optional argument -- in
that case we only want the last msg.id in References, so we don't really
need to call `gnus-split-references' to parse *all* the references and
build a list of them.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: gnus-util.el.diff --]
[-- Type: text/x-patch, Size: 679 bytes --]
--- ../../gnus/lisp/gnus-util.el Wed Jan 16 05:14:26 2002
+++ gnus-util.el Fri Jan 18 22:58:21 2002
@@ -479,10 +479,13 @@
If N, return the Nth ancestor instead."
(when (and references
(not (zerop (length references))))
- (let ((ids (inline (gnus-split-references references))))
- (while (nthcdr (or n 1) ids)
- (setq ids (cdr ids)))
- (car ids))))
+ (if n
+ (let ((ids (inline (gnus-split-references references))))
+ (while (nthcdr n ids)
+ (setq ids (cdr ids)))
+ (car ids))
+ (when (string-match "<[^> \t]+>\\'" references)
+ (match-string 0 references)))))
(defun gnus-buffer-live-p (buffer)
"Say whether BUFFER is alive or not."
next prev parent reply other threads:[~2002-01-18 23:42 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-16 2:12 Lars Magne Ingebrigtsen
2002-01-16 4:42 ` Russ Allbery
2002-01-19 23:25 ` Lars Magne Ingebrigtsen
2002-01-16 6:35 ` Jesper Harder
2002-01-19 23:25 ` Lars Magne Ingebrigtsen
2002-01-16 12:45 ` Simon Josefsson
2002-01-16 16:51 ` Josh Huber
2002-01-16 17:21 ` Karl Kleinpaste
2002-01-16 19:26 ` Steinar Bang
2002-01-17 2:06 ` Daniel Pittman
2002-01-17 17:04 ` Ami Fischman
2002-01-19 23:28 ` Lars Magne Ingebrigtsen
2002-01-20 19:11 ` Ami Fischman
2002-01-20 19:15 ` Lars Magne Ingebrigtsen
2002-01-20 20:05 ` Ami Fischman
2002-01-20 20:03 ` Lars Magne Ingebrigtsen
2002-01-20 20:33 ` Ami Fischman
2002-01-18 23:42 ` Jesper Harder [this message]
2002-01-19 11:38 ` Simon Josefsson
2002-01-27 0:30 Lars Magne Ingebrigtsen
2002-01-27 0:35 ` IPmonger
2002-01-27 0:45 ` Lars Magne Ingebrigtsen
2002-01-29 16:03 ` IPmonger
2002-01-30 8:53 ` Kai Großjohann
2002-01-30 16:42 ` IPmonger
2002-01-30 17:38 ` Kai Großjohann
2002-01-30 18:15 ` Lars Magne Ingebrigtsen
2002-01-30 18:42 ` Josh Huber
2002-02-04 23:35 ` IPmonger
2002-02-04 23:48 ` IPmonger
2002-02-04 23:57 ` Daniel Pittman
2002-01-30 22:02 ` Wes Hardaker
2002-01-30 22:09 ` IPmonger
2002-01-31 1:25 ` Wes Hardaker
2002-01-31 3:22 ` ShengHuo ZHU
2002-01-31 15:29 ` Wes Hardaker
2002-01-31 16:34 ` Steinar Bang
2002-01-31 16:54 ` Bjørn Mork
2002-01-31 20:50 ` Steinar Bang
2002-01-31 22:35 ` Bjørn Mork
2002-02-01 7:14 ` Steinar Bang
2002-02-01 9:17 ` Bjørn Mork
2002-02-01 10:00 ` Steinar Bang
2002-02-01 11:24 ` Bjørn Mork
2002-02-01 11:29 ` Simon Josefsson
2002-02-01 12:52 ` Steinar Bang
2002-02-01 13:40 ` Simon Josefsson
2002-02-01 14:12 ` Steinar Bang
2002-02-01 14:39 ` ShengHuo ZHU
2002-02-01 15:01 ` Simon Josefsson
2002-02-01 15:31 ` Steinar Bang
2002-02-01 14:59 ` Simon Josefsson
2002-02-01 15:18 ` Steinar Bang
2002-02-01 16:51 ` Wes Hardaker
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=m38zavw7j1.fsf@defun.localdomain \
--to=harder@ifa.au.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).