From: Eli Zaretskii <eliz@gnu.org>
To: Cecilio Pardo <cpardo@imayhem.com>
Cc: emacs-devel@gnu.org
Subject: Re: Drawing UI elements behind text
Date: Thu, 28 Nov 2024 08:53:30 +0200 [thread overview]
Message-ID: <86v7w7etn9.fsf@gnu.org> (raw)
In-Reply-To: <005e93b1-4b5b-4d59-9fc3-9bf9b9c29bdc@imayhem.com> (message from Cecilio Pardo on Wed, 27 Nov 2024 21:30:54 +0100)
> Date: Wed, 27 Nov 2024 21:30:54 +0100
> Cc: emacs-devel@gnu.org
> From: Cecilio Pardo <cpardo@imayhem.com>
>
> >> The very naive implementation I have now adds something like 5ms to each
> >> redisplay on a 1900px frame, and I hope to bring it down a lot from there.
> >
> > What takes 5ms, exactly? what kind of redisplay did you trigger, and
> > how did you trigger it?
>
> A minimal redisplay, just moving the cursor around. This takes less than
> 1ms, including the time to copy the back buffer to the window.
>
> When the segment drawing is activated (with tens of thousands of them,
> though only tens of them visible in some window) the process takes
> around 5ms.
>
> This process includes:
>
> - Making a new bitmap, and copy the result of redisplay to it.
> - Iterate trough lisp objects to prepare the segments, clip them and
> draw them to this bitmap.
>
> There is a lot of room here to make it faster.
OK, but I was more interested in more complex redisplay-related
scenarios. For example, what happens if you add a few lines of text
to the bottom of the window (by yanking several lines at once)? This
should cause Emacs to scroll the window, so that the text previously
shown at the top of the window will scroll out of the viewport, and
the yanked lines will be scrolled in. How long does this take, with
and without these segments?
Similarly, what are the timings (again, with and without these
segments) when you just move the cursor, but in a way that it goes out
of the window, or ends up in a display margin at the top of the
window, or in a partially-visible line at the bottom of the window?
Those (and other similar ones) are the scenarios where the display
engine activates its non-trivial optimization methods, and the
questions of interest related to that are:
. do we need to disable some of the optimizations when these
segments are on display (because their assumptions are
incompatible with how these segments are drawn)?
. how do these segments affect redisplay times in each such case,
after we disable the optimizations, if any, that are incompatible
with them?
These questions are prerequisites for deciding whether we need to make
this particular case faster by some special measures.
Thanks.
next prev parent reply other threads:[~2024-11-28 6:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-10 16:39 Drawing UI elements behind text Cecilio Pardo
2024-11-10 18:09 ` Jim Porter
2024-11-10 18:44 ` Eli Zaretskii
2024-11-10 19:06 ` Jim Porter
2024-11-10 19:22 ` Eli Zaretskii
2024-11-10 19:29 ` Jim Porter
2024-11-10 19:42 ` Eli Zaretskii
2024-11-24 23:37 ` JD Smith
2024-11-26 23:19 ` Cecilio Pardo
2024-11-27 14:36 ` Eli Zaretskii
2024-11-27 18:28 ` Cecilio Pardo
2024-11-27 18:58 ` Eli Zaretskii
2024-11-27 20:01 ` Cecilio Pardo
2024-11-27 20:12 ` Eli Zaretskii
2024-11-27 20:30 ` Cecilio Pardo
2024-11-28 6:53 ` Eli Zaretskii [this message]
2024-11-28 8:43 ` Cecilio Pardo
2024-11-28 9:57 ` Eli Zaretskii
2024-11-28 10:41 ` Cecilio Pardo
2024-11-28 11:56 ` Eli Zaretskii
2024-11-28 12:09 ` Cecilio Pardo
2024-11-27 21:15 ` JD Smith
2024-11-27 21:47 ` Cecilio Pardo
-- strict thread matches above, loose matches on Subject: below --
2024-11-27 2:31 JD Smith
2024-11-27 18:33 ` Cecilio Pardo
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=86v7w7etn9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cpardo@imayhem.com \
--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).