From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Cc: Dmitry Alexandrov <dag@gnui.org>
Subject: Re: Is font fallback slow over X11/ssh?
Date: Thu, 04 Jun 2020 17:01:37 -0400 [thread overview]
Message-ID: <jwvo8pyv9c4.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: 5zc62183.dag@gnui.org
>>>> Is font fallback slow over X11/ssh?
>>> FWIW, yes, it is. And thatʼs one of my reasons to prefer
>>> server-side font rendering for remote Emacs sessions.
>>> I. e. something like:
>>> $ emacs --xrm='Emacs.fontBackend: x'
>> Interesting. Do you have some explanation for why you find it more useful for remote sessions?
> No, in the sense that @yuri.v.khan@gmail.comʼs one is more thorough than mine.
My question was based on my foggy memory that back when client-side
fonts (xft) were introduced to the wonderful X11 world, there was some
article that came out explaining that while it requires sending the
bitmap of characters to the Xserver, it ends up being faster in remote
connections because the amount of data to send is not really larger than
the amount of data fetched from the Xserver for server-side fonts
(mostly in the form of the font-metrics) and suffers much less from
latency because it's "send-only" instead RPC.
>> Have you tried to *disable* the `x` fontBackend instead?
> Yes, in fact due to bug#25216 this is my normal setup.
>
> ! https://bugs.gnu.org/25216
> Emacs.fontBackend: xft,ftcrhb
>
> Why _it_ could help, I wonder now?
The idea was that it would avoid paying the cost of the `x` backend.
Stefan
next prev parent reply other threads:[~2020-06-04 21:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 12:11 Is font fallback slow over X11/ssh? Yuri Khan
2020-05-31 8:16 ` Dmitry Alexandrov
2020-05-31 13:13 ` Stefan Monnier
2020-06-04 17:24 ` Dmitry Alexandrov
2020-06-04 21:01 ` Stefan Monnier [this message]
2020-06-05 10:32 ` Dmitry Alexandrov
2020-06-05 15:22 ` Stefan Monnier
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=jwvo8pyv9c4.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=dag@gnui.org \
--cc=help-gnu-emacs@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.
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).