From: Todd M. <jm...@st...> - 2004-05-28 18:35:06
|
On Fri, 2004-05-28 at 10:56, John Hunter wrote: > >>>>> "Gary" == Gary Pajer <pa...@in...> writes: > > Gary> I took out a wristwatch and timed it instead of guessing. I > Gary> get three frames per second. It's about 4x from where we > Gary> started, but still slow. I guess I'm just underpowered, > Gary> although a couple of years ago this was a powerhouse. It > Gary> seems that matplotlib may not be suited to this task. I > Gary> don't think it should take 2 GHz just to power a stripchart. > > One more comment here, mainly for Todd. > > Todd, I get 34 FPS on anim.py with GTKAgg and only 21 FPS with the > anim_tk.py, where both scripts are doing the same thing. The profiler > reveals a good chunk of the time is in > > 103 2.300 0.022 2.300 0.022 tkagg.py:4(blit) > > This may be a tk limitation, but I just wanted to point it out to you > in case there are any optimizations you can apply to that function. I tried a few things, but I didn't find anymore performance blunders so barring the kind of optimization Perry mentioned, I think we're stuck. I think most of the time is going into Tk_PhotoPutBlock. > I'll include the anim_tk.py I'm using for profiling below. I only got 11-12 FPS (for tkagg) on a 1.7 Ghz Pentium-IV... Todd |