From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: npostavs@users.sourceforge.net, 28695@debbugs.gnu.org, bryan@bryan.sh
Subject: bug#28695: 26.0.60; Rendering lag spikes caused by double-buffering on Linux
Date: Mon, 09 Oct 2017 17:03:37 +0300 [thread overview]
Message-ID: <83shesquyu.fsf@gnu.org> (raw)
In-Reply-To: <859fe715-e455-128d-5fca-6f2df4ad0eaf@yandex.ru> (message from Dmitry Gutov on Mon, 9 Oct 2017 16:53:18 +0300)
> Cc: npostavs@users.sourceforge.net, bryan@bryan.sh, 28695@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Mon, 9 Oct 2017 16:53:18 +0300
>
> On 10/7/17 11:14 AM, Eli Zaretskii wrote:
>
> > Can some of you use a tool like perf to see whether the time taken by
> > XdbeSwapBuffers (called from xterm.c:show_back_buffer) indeed grows
> > significantly when going from the 2K class of resolutions to the 4K
> > class? And if it isn't XdbeSwapBuffers, then what takes most of the
> > time which causes that "stutter"?
>
> With some pointers on how to use perf, I'd be happy to do that
I think this page (which you probably already know about) is a good
starting point:
http://www.brendangregg.com/perf.html
> (or even without, if you're willing to wait).
There's no rush, so please take your time.
> But I'm not seeing a qualitative difference between a 4K fullscreen
> Emacs, a half-screen Emacs, or even Emacs with window resized further
> down: there are still minor stutters here. So I'm probably not the best
> person for this experiment.
Well, you saw a difference between a 4K display and a 2K display,
didn't you? All we need is to compare 2 situations and see where's
the extra time spent.
Maybe Bryan could also try the profile, as he reported a significant
difference.
Thanks.
next prev parent reply other threads:[~2017-10-09 14:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 3:10 bug#28695: 26.0.60; Rendering lag spikes caused by double-buffering on Linux Bryan Gilbert
2017-10-04 7:53 ` Eli Zaretskii
2017-10-04 9:04 ` martin rudalics
2017-10-04 9:32 ` Eli Zaretskii
2017-10-04 11:21 ` Bryan Gilbert
2017-10-04 11:36 ` Eli Zaretskii
2017-10-04 12:02 ` Bryan Gilbert
2017-10-04 12:31 ` Eli Zaretskii
2017-10-05 13:36 ` Dmitry Gutov
2017-10-05 14:01 ` Eli Zaretskii
2017-10-05 14:02 ` Noam Postavsky
2017-10-07 7:53 ` Dmitry Gutov
2017-10-07 8:14 ` Eli Zaretskii
2017-10-09 13:53 ` Dmitry Gutov
2017-10-09 14:03 ` Eli Zaretskii [this message]
2017-10-15 22:55 ` Dmitry Gutov
2017-10-16 2:30 ` Eli Zaretskii
2017-10-26 23:19 ` Dmitry Gutov
2017-10-28 9:33 ` Eli Zaretskii
2017-10-28 21:47 ` bug#28695: 26.0.60; Rendering lag spikes caused by double-buffering on GNU/Linux Richard Stallman
2017-10-05 14:26 ` bug#28695: 26.0.60; Rendering lag spikes caused by double-buffering on Linux Bryan Gilbert
2022-04-23 13:46 ` Lars Ingebrigtsen
2022-05-22 11:28 ` Lars 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=83shesquyu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28695@debbugs.gnu.org \
--cc=bryan@bryan.sh \
--cc=dgutov@yandex.ru \
--cc=npostavs@users.sourceforge.net \
/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.