unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: wyuenho@gmail.com, emacs-devel@gnu.org
Subject: Re: How to measure frame rate in fps?
Date: Mon, 07 Jun 2021 15:33:25 +0300	[thread overview]
Message-ID: <837dj5hn1m.fsf@gnu.org> (raw)
In-Reply-To: <bc050224-45f1-bcde-cdeb-3fc5f197fc5a@yandex.ru> (message from Dmitry Gutov on Mon, 7 Jun 2021 02:31:50 +0300)

> Cc: wyuenho@gmail.com, emacs-devel@gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Mon, 7 Jun 2021 02:31:50 +0300
> 
> I have one scenario, which I run with toolbar disabled, then enabled, 
> then disabled, then enabled again. With a (benchmark-progn ...) wrapped 
> around a (redisplay) call, to note how long it really takes in practice.
> 
> I'm saying that the buffer, or other window configuration, don't change 
> at those points, so the toolbar likely doesn't need to be re-rendered, 
> and so the extra overhead is surprising. And that the toolbar taking 
> 10-15ms to re-render isn't great either in any case.

But in the profile you showed we didn't see any evidence of
significant CPU usage by functions that redraw the GTK toolbar.  So
I'm not sure the overhead is due to redrawing the toolbar, although it
might be _triggered_ by the presence of the toolbar.

> It's the difference, computed very roughly. Let me show you the contents 
> of the Messages buffer. The times printed are reported by the 
> (benchmark-progn (redisplay)) form:

How do you reconcile this with the 00.00% that GTK functions took?

Can you see what does 'perf' say about functions from gtkutil.c that
are related to toolbar redisplay?



  reply	other threads:[~2021-06-07 12:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-31 13:03 How to measure frame rate in fps? Jimmy Yuen Ho Wong
2021-06-01 10:00 ` Arthur Miller
2021-06-01 11:43 ` Eli Zaretskii
2021-06-01 14:18   ` Dmitry Gutov
2021-06-01 14:43     ` Eli Zaretskii
2021-06-01 15:00       ` Dmitry Gutov
2021-06-01 15:35         ` Eli Zaretskii
2021-06-01 21:31           ` Dmitry Gutov
2021-06-02  2:29             ` Eli Zaretskii
2021-06-06  2:09               ` Dmitry Gutov
2021-06-06  6:11                 ` Eli Zaretskii
2021-06-06 12:00                   ` Dmitry Gutov
2021-06-06 12:36                     ` Eli Zaretskii
2021-06-06 16:48                       ` Dmitry Gutov
2021-06-06 17:19                         ` Eli Zaretskii
2021-06-06 23:31                           ` Dmitry Gutov
2021-06-07 12:33                             ` Eli Zaretskii [this message]
2021-06-06 18:10                         ` Stefan Monnier
2021-06-06 23:35                           ` Dmitry Gutov

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=837dj5hn1m.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=wyuenho@gmail.com \
    /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).