From: Yiming Chen <me@yiming.dev>
To: emacs-devel@gnu.org
Subject: [NS] Emacs 28 (IOSurface) renders much slower than Emacs 27 on macOS Big Sur
Date: Sun, 02 May 2021 21:40:03 +0800 [thread overview]
Message-ID: <m1wnshz02i.fsf@yiming.dev> (raw)
[-- Attachment #1: Type: text/html, Size: 8511 bytes --]
[-- Attachment #2: Type: text/plain, Size: 3442 bytes --]
Hi there!
I know that we've switched to a IOSurface based rendering for nsterm in
master branch.
Now master renders more precisely than emacs-27 (i.e. less flickers or
blank screens.)
But I feel that its rendering performance is much worse due to the new
buffering mechanism backed by IOSurface.
Several cases that I can feel this worse performance:
1. moving a maximized emacs frame from a larger screen to a smaller
screen (I use hammerspoon to do that)
I can see the emacs-28 frame shrink to the smaller screen size, then
move to the smaller screen
2. scrolling
I set `scroll-conservatively' to 101 in order to achieve the
smooth-scrolling effect.
When I scroll down a large text buffer constantly (hold `j' in
evil-mode or `C-n' in emacs-mode),
emacs-28 hangs more times than emacs-27 (emacs-27 scrolls very
smoothly except it would flicker from time to time)
See also
<https://www.reddit.com/r/emacs/comments/mhdjxb/macos_emacs_with_metal_support/guhbck4/>
for a previous discussion.
3. child-frame
child-frame like company-box appears more slowly in emacs-28 than
emacs-27
Sorry I haven't found a way to measure the rendering performance except
the `scroll-up-benchmark' script from Alan Third in the reddit comment
mentioned above.
I think this poor rendering performance obscures the improvements
brought by native-compile.
So I want to fix this performance issue and make Emacs runs on macOS as
fast as on Linux.
I've spent the last several days trying to understand how nsterm works
and if we can use a more efficient rendering API.
But I failed completely, mostly because I have no Cocoa development
experience before.
Here are the 3 steps I want to take to improve the rendering
performance:
1. Try to restore the nsterm behavior from Emacs27 (which is much
simpler than master IMHO), and start again from there
I've reverted the code and made it compile (see
<https://github.com/emacs-mirror/emacs/compare/master...dsdshcym:revert-to-emacs-27-nsterm>)
But Emacs failed to start and raised an error `Font ‘Menlo’ is not
defined'
2. Use layer-based view for rendering
I found that macvim also faced the similar issue when macOS 10.14
came out (<https://github.com/macvim-dev/macvim/issues/751>).
They used NSImage to implement a double rendering solution
(<https://github.com/macvim-dev/macvim/pull/757/files>), which was
also slower than before.
Then they switched from NSImage to layer-based view in
<https://github.com/macvim-dev/macvim/commit/dba6293677e0633917e3054cfddec1293e5ab3fb>.
So I wonder if we can do the same.
3. Switch to CALayer (Core Animation) to use GPU (Metal) rendering for
even better performance than before
If 2 (layer-based view) is possible, then I hope we can leverage
CALayer to make nsterm renders even faster.
I was so desperate about this issue, so I also tried other window
systems on macOS:
1. emacs-pgtk (<https://github.com/masm11/emacs/issues/95>):
technically emacs-pgtk should work on macOS with gtk3, but the
performance was even worse
2. emacs-ng + webrender
(<https://github.com/emacs-ng/emacs-ng/issues/207>)
webrender hasn't been working on macOS neither
If anyone can point a direction for me so I can investigate more, that
would be the best.
Thanks in advance!
Cheers,
Yiming
next reply other threads:[~2021-05-02 13:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-02 13:40 Yiming Chen [this message]
2021-05-02 22:50 ` [NS] Emacs 28 (IOSurface) renders much slower than Emacs 27 on macOS Big Sur Alan Third
2021-06-01 2:29 ` Yiming Chen
2021-06-03 21:41 ` Alan Third
2021-06-04 12:30 ` Yiming Chen
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=m1wnshz02i.fsf@yiming.dev \
--to=me@yiming.dev \
--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).