From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Eli Zaretskii <eliz@gnu.org>
Cc: dmantipov@yandex.ru, emacs-devel@gnu.org
Subject: Re: Extra info about 109170
Date: Tue, 24 Jul 2012 18:11:11 -0400 [thread overview]
Message-ID: <jwvipdcersl.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83lii9ksb1.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 24 Jul 2012 20:00:34 +0300")
>> The problem was that kill-buffer was taking up more than 10% of the time
>> of execution, which is simply unjustified. I only know of 2 ways to fix
>> such a problem:
>> - speed up kill-buffer.
>> - call kill-buffer less often.
>> (tho I guess you can also "fix" it by slowing down everything else,
>> but that's not very interesting, is it?).
>> So unless you mean that the right thing to do was to reduce calls to
>> kill-buffer, I don't know what else you might have wanted.
> I think, if we want to speed up byte compilation, the right thing is
> to speed the compilation itself, not buffer-killing whose relevance to
> byte compilation is, well, questionable.
I'm not sure if that means you disagree with my above analysis (if so,
I don't know with which part), or if you do agree with it but think that
the solution should be to reduce the number of calls to kill-buffer.
Stefan
next prev parent reply other threads:[~2012-07-24 22:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 16:12 Extra info about 109170 Dmitry Antipov
2012-07-21 7:04 ` Stefan Monnier
2012-07-21 8:15 ` Eli Zaretskii
2012-07-22 9:57 ` Stefan Monnier
2012-07-22 15:18 ` Eli Zaretskii
2012-07-23 8:55 ` Stefan Monnier
2012-07-23 10:05 ` joakim
2012-07-23 10:56 ` Nix
2012-07-23 15:31 ` Eli Zaretskii
2012-07-23 23:06 ` Stefan Monnier
2012-07-24 17:00 ` Eli Zaretskii
2012-07-24 22:11 ` Stefan Monnier [this message]
2012-07-25 3:00 ` Eli Zaretskii
2012-07-25 23:32 ` Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvipdcersl.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=dmantipov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).