John Hunter wrote:
On Jan 15, 2008 7:46 AM, Michael Droettboom [EMAIL PROTECTED] wrote:
Ah -- just thought of something else.
If I adjust simple_plot_fps.py to have 100,000 data points rather than
1,000 I see something that starts to match with what you're seeing:
GtkAgg:
wallclock:
Christopher Barker wrote:
Michael Droettboom wrote:
It's sort of a pygtk issue -- it
would have to be rewritten to take numpy arrays
not quite -- it would have to be re-written to use the array interface,
which is different, as that can be done without requiring numpy, or its
headers.
All very helpful information. Thanks.
This is probably something to move to the pygtk list. Personally, I don't
consider it a high priority since the Gdk backend is limited in a number of
other ways. Maybe someone more motivated (who uses X remotely, for instance)
wants to take the charge.
Michael Droettboom wrote:
It's sort of a pygtk issue -- it
would have to be rewritten to take numpy arrays
not quite -- it would have to be re-written to use the array interface,
which is different, as that can be done without requiring numpy, or its
headers.
which is probably
unlikely
On Jan 15, 2008 7:46 AM, Michael Droettboom [EMAIL PROTECTED] wrote:
Ah -- just thought of something else.
If I adjust simple_plot_fps.py to have 100,000 data points rather than
1,000 I see something that starts to match with what you're seeing:
GtkAgg:
wallclock: 4.23297405243
user: 3.33
Hi,
I don't have conclusive proof, .. but I suspect that the draw() of a
graph in a pyGTK application is order of magnitudes slower than I can
plot the same data in the default Tk graphing widget.
i.e. 5 sec in tk, ... and 1 minute in gtk
Obvious question, ... is this a know issue?
Is
In my own tests, using the built-in GUI windows I get the following
numbers on the simple_plot_fps.py speed test (which essentially tests
redrawing speed, which is pretty GUI-backend dependent, as opposed to
the first drawing operation which involves more common code):
GtkAgg:
wallclock:
Ah -- just thought of something else.
If I adjust simple_plot_fps.py to have 100,000 data points rather than
1,000 I see something that starts to match with what you're seeing:
GtkAgg:
wallclock: 4.23297405243
user: 3.33
fps: 23.6240522057
Gtk:
wallclock: 15.0203828812
user: 14.92
fps:
