From: Ted Stern <dodecatheon@gmail.com>
Subject: why does message-generate-headers take so long?
Date: Tue, 22 Aug 2006 15:41:56 -0700 [thread overview]
Message-ID: <lsphd04mlzf.fsf@saturna.ca.boeing.com> (raw)
Hi all,
Sending a message from CVS Emacs + CVS Gnus on Red Hat Enterprise
Linux Workstation 4 (x86_64) takes quite a bit of time, so I profiled
all message-* functions to see where the time hog was. I'm inserting
just the top 9 results:
,----[ elp-results ]
| Function Name Call Count Elapsed Time Average Time
| ============================================== ========== ============ ============
| message-send-and-exit 1 20.467676 20.467676
| message-send 1 20.467588 20.467588
| message-send-via-mail 1 20.24165 20.24165
| message-send-mail 1 20.241641 20.241641
| message-generate-headers 2 20.131608 10.065804
| message-send-mail-with-sendmail 1 0.1094629999 0.1094629999
| message-tab 1 0.076816 0.076816
| message-expand-name 1 0.076688 0.076688
| message-mail 1 0.069009 0.069009
`----
Clearly, the most time is being spent in message-generate-headers, and
the other long times are accumulated with it. There are a lot of
(while (re-search-forward)) loops, but this message was just a few
lines long!
Can anyone think of a reason why that routine would take so long? Why
is it being called twice? Is there any way to speed it up?
Ted
--
dodecatheon at gmail dot com
Frango ut patefaciam -- I break so that I may reveal
next reply other threads:[~2006-08-22 22:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 22:41 Ted Stern [this message]
2006-08-23 4:24 ` Andreas Seltenreich
2006-08-23 8:43 ` Simon Josefsson
2006-08-23 13:47 ` Wes Hardaker
2006-08-23 15:15 ` Simon Josefsson
2006-08-23 15:34 ` gdt
2006-08-23 8:34 ` Elias Oltmanns
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=lsphd04mlzf.fsf@saturna.ca.boeing.com \
--to=dodecatheon@gmail.com \
/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).