all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Paul Eggert <eggert@cs.ucla.edu>,
	 Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Tooltips GC overhead
Date: Wed, 29 Jul 2015 20:05:45 +0200	[thread overview]
Message-ID: <55B915F9.7040802@gmx.at> (raw)
In-Reply-To: <55B90321.2000501@cs.ucla.edu>

 >> Does that mean I have to recompile all elisp files?
 >
 > No, just the .o files, src/temacs, src/bootstrap-emacs, and src/emacs.

Good.  I did that.

 >> Anyway.  If you do `profiler-start', move the mouse over your mode line
 >> for a few seconds so that tooltips show up a couple of times and then do
 >> `profiler-report' and look at the results: Can you tell me from your
 >> report where `tooltip-show' allocates more than half of the bytes it
 >> allocates if _not_ in `x-show-tip'?
 >
 > I presume those bytes are allocated directly by tooltip-show.  By "directly" I mean via a function written in C, e.g., "cons".

There are one call of `copy-sequence', two calls of `stringp', three of
`setf', one of `propertize' and one of `selected-frame'.  Together these
would allocate some 20 million bytes?

OTOH the `copy-sequence', `face-attribute' and `alist-get' calls get
nowhere listed.

martin



  reply	other threads:[~2015-07-29 18:05 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55B915F9.7040802@gmx.at \
    --to=rudalics@gmx.at \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.