Kevin Horton wrote:
> I'm not sure where the bottleneck lies
I don't know any details of either of the GTK back-ends, but this sounds
like what I'd expect.
With the *Agg backends, the rendering is done by Agg, generating an
image in memory, and then the entire image is passed (one way or
another) to the X-server to render. This is pretty quick with a local
X-server, but it is a lot of data to pass over a network.
In contrast, the with the non-Agg back ends, the rendering is done by
the X-server, with MPL passing it drawing commands, rather than images.
In general, there is a lot less data to pas over the network with way,
so it's going to be faster.
> I also want to note that the GTK
> backend is useful to some people, and hope that it will continue to
> be supported (I seem to recall one mention that it was little used).
This is a good point. In general, the Agg back-ends produce nicer an
more consistent results, and, on local machines, performance is just
fine, but in a remote X-session, there are real advantages to using X
for the rendering. The same probably applies to the TK and Wx back-ends
Christopher Barker, Ph.D.
NOAA/OR&R/HAZMAT (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception