Re: [matplotlib-devel] Speed improvements on the branch

2007-11-15 Thread Michael Droettboom
Michael Droettboom wrote: John Hunter wrote: log_demo.py 1.769 2.011 0.242113% Here is another area where there is an important difference. Panning and zooming interactively with log scaling is much slower on the branch, presumably because you have to r

Re: [matplotlib-devel] Speed improvements on the branch

2007-11-15 Thread Michael Droettboom
John Hunter wrote: > On Nov 15, 2007 1:51 PM, Michael Droettboom <[EMAIL PROTECTED]> wrote: > >> Very odd. I've been running my own very similar benchmark as I've been >> going, and the two code bases perform quite similarly. The branch >> continues to cache the markers in more or less the same

Re: [matplotlib-devel] Speed improvements on the branch

2007-11-15 Thread John Hunter
On Nov 15, 2007 1:51 PM, Michael Droettboom <[EMAIL PROTECTED]> wrote: > Very odd. I've been running my own very similar benchmark as I've been > going, and the two code bases perform quite similarly. The branch > continues to cache the markers in more or less the same way as on the > trunk. He

Re: [matplotlib-devel] Speed improvements on the branch

2007-11-15 Thread Michael Droettboom
John Hunter wrote: > On Nov 15, 2007 12:53 PM, Michael Droettboom <[EMAIL PROTECTED]> wrote: > >> Thought some of you may be interested to know that the speed on the >> branch is getting much better. Whereas earlier the branch was about 2x >> slower than the trunk, now most things are close to eq

Re: [matplotlib-devel] Speed improvements on the branch

2007-11-15 Thread John Hunter
On Nov 15, 2007 12:53 PM, Michael Droettboom <[EMAIL PROTECTED]> wrote: > Thought some of you may be interested to know that the speed on the > branch is getting much better. Whereas earlier the branch was about 2x > slower than the trunk, now most things are close to equal with the trunk > speed

Re: [matplotlib-devel] speed

2007-11-12 Thread Eric Firing
Michael Droettboom wrote: > John Hunter wrote: >> On Nov 9, 2007 1:12 PM, Michael Droettboom <[EMAIL PROTECTED]> wrote: >> >>> I've committed my changes on the transforms branch so you can play with >>> it -- I'm holding off on changing the trunk due to the pending release. >>> But if everyone agre

Re: [matplotlib-devel] speed

2007-11-09 Thread Paul Kienzle
On Fri, Nov 09, 2007 at 01:39:10PM -0600, John Hunter wrote: > On Nov 9, 2007 1:12 PM, Michael Droettboom <[EMAIL PROTECTED]> wrote: > > > I've committed my changes on the transforms branch so you can play with > > it -- I'm holding off on changing the trunk due to the pending release. > > But if

Re: [matplotlib-devel] speed

2007-11-09 Thread Michael Droettboom
Sorry, I didn't explain the benchmark (which was in an off-list e-mail to Eric.) The "fps" value in these benchmarks is the frames-per-second you get when updating the range of the axes (approximately what to expect from an interactive pan/zoom operation). The "init" time is the time it takes

Re: [matplotlib-devel] speed

2007-11-09 Thread william ratcliff
Michael, Have you looked at the speed of zooming in and out with pcolormesh? On Nov 9, 2007 3:33 PM, Michael Droettboom <[EMAIL PROTECTED]> wrote: > Darren Dale wrote: > > On Friday 09 November 2007 03:26:12 pm Michael Droettboom wrote: > >> Eric Firing wrote: > >>> Mike, > >>> > >>> Thank you fo

Re: [matplotlib-devel] speed

2007-11-09 Thread Michael Droettboom
Darren Dale wrote: > On Friday 09 November 2007 03:26:12 pm Michael Droettboom wrote: >> Eric Firing wrote: >>> Mike, >>> >>> Thank you for once again blasting out such an array of improvements. >>> Regarding implementation and API details, such as what should go in >>> imshow versus pcolor versus

Re: [matplotlib-devel] speed

2007-11-09 Thread Darren Dale
On Friday 09 November 2007 03:26:12 pm Michael Droettboom wrote: > Eric Firing wrote: > > Mike, > > > > Thank you for once again blasting out such an array of improvements. > > Regarding implementation and API details, such as what should go in > > imshow versus pcolor versus something with another

Re: [matplotlib-devel] speed

2007-11-09 Thread Michael Droettboom
Eric Firing wrote: > Mike, > > Thank you for once again blasting out such an array of improvements. > Regarding implementation and API details, such as what should go in > imshow versus pcolor versus something with another name, I would like to > review the situation (and your branch) and come u

Re: [matplotlib-devel] speed

2007-11-09 Thread Eric Firing
Mike, Thank you for once again blasting out such an array of improvements. Regarding implementation and API details, such as what should go in imshow versus pcolor versus something with another name, I would like to review the situation (and your branch) and come up with a recommendation, but I

Re: [matplotlib-devel] speed

2007-11-09 Thread Eric Firing
John Hunter wrote: > On Nov 9, 2007 1:12 PM, Michael Droettboom <[EMAIL PROTECTED]> wrote: > >> I've committed my changes on the transforms branch so you can play with >> it -- I'm holding off on changing the trunk due to the pending release. >> But if everyone agrees on the way to expose this, it

Re: [matplotlib-devel] speed

2007-11-09 Thread Michael Droettboom
John Hunter wrote: > On Nov 9, 2007 1:12 PM, Michael Droettboom <[EMAIL PROTECTED]> wrote: > >> I've committed my changes on the transforms branch so you can play with >> it -- I'm holding off on changing the trunk due to the pending release. >> But if everyone agrees on the way to expose this, it

Re: [matplotlib-devel] speed

2007-11-09 Thread John Hunter
On Nov 9, 2007 1:12 PM, Michael Droettboom <[EMAIL PROTECTED]> wrote: > I've committed my changes on the transforms branch so you can play with > it -- I'm holding off on changing the trunk due to the pending release. > But if everyone agrees on the way to expose this, it would be nice to > merge

Re: [matplotlib-devel] speed

2007-11-09 Thread Michael Droettboom
[To summarize an off-list conversation -- Eric and I had been discussing ways to speed up pcolor plots. After some improvements, quadmeshes are still about a factor of 2 slower on the branch than on the trunk. His use case often involves the simpler problem of rectilinear meshes, which can be