From: Daniel Pittman <daniel@rimspace.net>
Cc: ding@gnus.org
Subject: Re: Time in Redisplay
Date: Mon, 09 Sep 2002 11:25:35 +1000 [thread overview]
Message-ID: <8765xg0x9s.fsf@enki.rimspace.net> (raw)
In-Reply-To: <oydelc4vq0m.fsf@bert.cs.rice.edu> (Scott A Crosby's message of "08 Sep 2002 03:34:17 -0500")
On 08 Sep 2002, Scott A. Crosby wrote:
> On 08 Sep 2002 03:29:39 -0500, Scott A Crosby <scrosby@cs.rice.edu>
> writes:
>
>> Hello, I'm using:
>>
>> XEmacs 21.4 (patch 6) "Common Lisp" [Lucid] (i386-debian-linux, Mule)
>> of Sat Apr 6 2002 on eeyore Gnus v5.8.8
>>
>> I've been using my session
>
> My apologies.... I was about to comment in the lunacy of this profile:
>
> Function Name Ticks %/Total Call Count
> =============================================== ===== ======= ==========
> (in redisplay) 374494 67.116
> (in garbage collection) 51996 9.319
> next-single-property-change 31473 5.641 9569955
> (processing events at top level) 16849 3.020
> string-match 7443 1.334 6500752
> select-frame 7188 1.288 29466166
> ad-Orig-re-search-forward 5997 1.075 2736930
> kill-all-local-variables 5560 0.996 200237
> lazy-lock-fontify-window 3525 0.632 9593636
> get-text-property 3082 0.552 19423541
>
> when I noticed I was accidently running MULE. Does non-MULE run
> redisplay signifigantly faster?
Yes.
Well, it does some things faster because it has fixed length character
sequences in the buffers, not variable length. This can result in better
performance.
Daniel
--
When there is a gap betweem one's real and one's declared aims, one turns, as
it were, instinctively to long words and exhausted idioms, like a cuttlefish
squirting out ink.
-- George Orwell
prev parent reply other threads:[~2002-09-09 1:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-08 8:29 Scott A Crosby
2002-09-08 8:34 ` Scott A Crosby
2002-09-09 1:25 ` Daniel Pittman [this message]
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=8765xg0x9s.fsf@enki.rimspace.net \
--to=daniel@rimspace.net \
--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).