> Could you post the script you are using to do the
> profiling?
This is the code that I was using
from pylab import *
import numpy
figure()
x=numpy.arange(20)
y=1+x**2
n = 4
for i in range(n*n):
subplot(n,n,i+1)
bar(x,y,log=True)
xlim(-5,25)
ylim(1,1e4)
> The call to subplot/plot/bar should not trigger a draw, unless
> "interactive" is set to True
I was doing the profiling with "interactive" set to True (both for the Agg
backends and for the Mac OS X native backend). With "interactive" set to False,
I don't see any significant speed difference between Agg and the native backend.
> Interactive is not the best word, but it is the rc
> parameter meaning
> "you are using mpl from the interactive prompt and
> want every pyplot
> command to update the plot". If the macosx backend is
> not doing this it should.
In its current form, the MacOSX backend assumes that mpl is being used from the
interactive prompt and the plot is updated whenever there are no further Python
commands (in other words, when Python is waiting for the user to type in the
next Python command). Maybe this is a naive question, but why would a user want
every pyplot command to update the plot?
--Michiel.
------------------------------------------------------------------------------
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
