Re: XEmacs 21.5 much slower remotely?
On Fri, 11 Sep 2009 10:37:21 +0900, Stephen wrote:
Adam Sjøgren writes:
> So the culprit in my particular case seems to be xft.
I can think of a number of possibilities.
(1) I believe that the Xrender extension caches "glyph collections" in
the server (effectively, it caches fonts). So it should be as
efficient as the server-side legacy fonts as long as glyphs are
sent to the server "as needed". Maybe your server doesn't
implement Xrender? (Look for RENDER in the list of extensions
returned by xdpyinfo.) Nothing XEmacs can do about this; you'll
have to live without Xft.
That isn't it:
$ xdpyinfo | grep RENDER
RENDER
$
(on both machines involved, so I didn't look on the wrong one :-))
(2) Font instances are supposed to be cached in XEmacs, but it looks
to me like the same fonts are repeatedly instantiated. This would
probably defeat the caching. I think this is unlikely to be the
culprit, as this happens only a few hundred times (I think once
per face creation, basically). But it could be that the cache is
quite limited in size, and every time a new face comes in the old
one's cache data gets overwritten.
Sounds intriguing. Do you have any pointers on how to test if this is
the case?
(3) Something about Xft is triggering redisplay aborts. The abort
counter I suggested might tell you about that.
I will see if I can give it a try.
(4) Something else. :-)
... and take you up on this one later :-)
Best regards,
Adam
--
"My internal clock is on Tokyo time." Adam Sjøgren
asjo(a)koldfront.dk
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta