From: Wes Hardaker <wjhardaker@ucdavis.edu>
Subject: why so many kill-all-local-variables
Date: 22 Jul 1999 15:32:06 -0700 [thread overview]
Message-ID: <sdyag8mi3d.fsf@oakdale.ucdavis.edu> (raw)
I have a annoyingly slow machine at work (ok, its not that bad, but
its not great). So I decided to see what profiling gave me...
Not surprisingly, searching came out high on top (no surprise), but
garbage collection and kill-all-local-variables dominated the scene.
This made me wonder why killing the local variables was needed so
much? I would think that you merely add to them or don't? I'm
wondering if this is a major source of the garbage collection that is
taking place (doubt it) and if they can be reduced?
Function Name Ticks %/Total Call Count
================================================ ===== ======= ==========
(in garbage collection) 3412 52.760
kill-all-local-variables 293 4.531 1824
re-search-forward 248 3.835 35824
get-buffer-create 192 2.969 3640
Function Name Ticks %/Total Call Count
================================================ ===== ======= ==========
(in garbage collection) 2505 53.434
kill-all-local-variables 222 4.735 1366
re-search-forward 178 3.797 26614
get-buffer-create 140 2.986 2716
Function Name Ticks %/Total Call Count
================================================ ===== ======= ==========
(in garbage collection) 3412 53.014
kill-all-local-variables 293 4.553 1824
re-search-forward 248 3.853 35822
get-buffer-create 191 2.968 3629
--
"Ninjas aren't dangerous. They're more afraid of you than you are of them."
next reply other threads:[~1999-07-22 22:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-22 22:32 Wes Hardaker [this message]
1999-08-27 21:38 ` Lars Magne Ingebrigtsen
1999-09-01 16:59 ` Wes Hardaker
1999-09-25 7:52 ` Lars Magne Ingebrigtsen
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=sdyag8mi3d.fsf@oakdale.ucdavis.edu \
--to=wjhardaker@ucdavis.edu \
/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).