Re: Why is Emacs so slow when used remotely?

[David Kastrup <dak@gnu.org>]

pjb@informatimago.com (Pascal J. Bourguignon) writes:

> David Kastrup <dak@gnu.org> writes:
>
>> pjb@informatimago.com (Pascal J. Bourguignon) writes:
>>
>>> Tim X <timx@nospam.dev.null> writes:
>>>
>>>> A few things to try ...
>>>>
>>>> 1. turn off tooltip mode
>>>
>>> Yes. Anything graphic.
>>>
>>>
>>>> 2. Try running with -nw to turn off X and only have a terminal UI
>>>> and see what the performance is like. this will let you know if
>>>> the problem is basic emacs or the X protocol stuff
>>>
>>> This is not useful, if you only work with text.  The X protocol is
>>> not significantly worse than any other terminal protocol to send
>>> over text.
>>
>> Font rendering/antialiasing/composition nowadays happens mostly at
>> the client side if I am not mistaken.  That makes the X protocol
>> much worse even with text.
>
> That's not what I observe.  It's possible for an application to deal
> with characters itself and send bitmaps but normally, and it looks
> like it's what emacs does, it sends only the strings and the font
> rendering is done in the X server.

For bitmap fonts.  I don't think the X protocol channels antialiased
fonts yet.  Usually xfs (the font server) runs on the client side of the
connection.

-- 
David Kastrup