From: martin rudalics <rudalics@gmx.at>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Tooltips GC overhead
Date: Sat, 01 Aug 2015 12:49:56 +0200 [thread overview]
Message-ID: <55BCA454.6050208@gmx.at> (raw)
In-Reply-To: <55B94267.5050208@cs.ucla.edu>
> Weird. Perhaps my guess about your problem was wrong, though there is
> clearly a bug there in computing percentages, which I'll see if I can
> fix.
Whatever you've done: With latest trunk/master all percentages come up
correctly. So many thanks for your efforts.
The following excerpt from `profiler-report' still exhibits the other
problem:
- timer-event-handler 21,655,992 90%
- apply 21,655,992 90%
- tooltip-timeout 21,655,992 90%
- run-hook-with-args-until-success 21,655,992 90%
- tooltip-help-tips 21,655,992 90%
- tooltip-show 21,655,992 90%
- x-show-tip 1,119,104 4%
- face-set-after-frame-default 1,119,104 4%
- face-spec-recalc 1,102,240 4%
+ face-spec-reset-face 1,045,708 4%
+ face-spec-set-2 21,924 0%
+ face-spec-choose 15,816 0%
face-list 5,220 0%
+ command-execute 1,399,342 5%
+ redisplay_internal (C function) 870,687 3%
+ tooltip-show-help 8,352 0%
... 0 0%
The absolute value for `x-show-tip' is surely wrong. `x-show-tip'
is responsible for 90% (or maybe 89%) of the allocations.
Thanks again, martin
next prev parent reply other threads:[~2015-08-01 10:49 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 12:45 Tooltips GC overhead martin rudalics
2015-07-28 13:53 ` Eli Zaretskii
2015-07-28 15:09 ` martin rudalics
2015-07-28 23:51 ` Stefan Monnier
2015-07-29 7:18 ` martin rudalics
2015-07-29 14:29 ` Paul Eggert
2015-07-29 15:40 ` martin rudalics
2015-07-29 16:33 ` Eli Zaretskii
2015-07-29 18:05 ` martin rudalics
2015-07-29 21:15 ` Paul Eggert
2015-07-30 6:00 ` martin rudalics
2015-07-30 7:08 ` martin rudalics
2015-07-30 7:19 ` Paul Eggert
2015-07-30 9:05 ` martin rudalics
2015-07-30 16:36 ` Eli Zaretskii
2015-07-30 19:53 ` martin rudalics
2015-07-30 23:09 ` Stefan Monnier
2015-07-30 23:33 ` Drew Adams
2015-07-31 6:48 ` Eli Zaretskii
2015-07-31 6:47 ` Eli Zaretskii
2016-03-06 9:21 ` martin rudalics
2016-03-08 8:02 ` martin rudalics
2015-08-01 10:49 ` martin rudalics [this message]
2015-08-03 10:34 ` Stefan Monnier
2015-08-03 14:56 ` Eli Zaretskii
2015-08-03 21:13 ` Stefan Monnier
2015-08-04 2:38 ` Eli Zaretskii
2015-08-04 7:31 ` Stefan Monnier
2015-08-04 13:28 ` Eli Zaretskii
2015-08-07 14:52 ` Stefan Monnier
2015-08-07 15:23 ` Eli Zaretskii
2015-08-07 17:26 ` Stefan Monnier
2015-08-07 18:20 ` Eli Zaretskii
2015-08-07 21:25 ` Stefan Monnier
2015-08-08 6:46 ` Eli Zaretskii
2015-08-08 7:01 ` David Kastrup
2015-08-07 18:26 ` Paul Eggert
2015-08-07 18:59 ` Eli Zaretskii
2015-08-08 13:41 ` Nix
2015-08-08 16:10 ` Stefan Monnier
2015-08-08 16:13 ` David Kastrup
2015-08-10 17:05 ` Nix
2015-08-10 17:44 ` David Kastrup
2015-07-29 16:45 ` Paul Eggert
2015-07-29 18:05 ` martin rudalics
2015-07-29 21:17 ` Paul Eggert
2015-07-30 6:00 ` martin rudalics
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=55BCA454.6050208@gmx.at \
--to=rudalics@gmx.at \
--cc=eggert@cs.ucla.edu \
--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).