Stephen J. Turnbull wrote:
> I just tried turning off xft (--without-xft) and with this 21.5
build
> the display updates quickly over the ADSL-line for me.
>
> 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.
(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.
(3) Something about Xft is triggering redisplay aborts. The abort
counter I suggested might tell you about that.
(4) Something else. :-)
If the server doesn't implement the Render extension, anti-aliasing
requires a read-modify-write cycle, so rendering speed will be
inversely proportional to latency (i.e. you get one glyph per
round-trip).
Xft is at least smart enough not to do this for non-AA text, so I
suggest disabling anti-aliasing (via FontConfig) to see if that
improves matters.
--
Glynn Clements <glynn(a)gclements.plus.com>
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta