Darren Dale wrote:
> On Thursday 16 August 2007 5:25:47 pm Fernando Perez wrote:
>> On 8/16/07, Darren Dale <[EMAIL PROTECTED]> wrote:
>>> On Thursday 16 August 2007 03:33:37 pm Darren Dale wrote:
>>>> On Thursday 16 August 2007 03:15:39 pm Fernando Perez wrote:
>>>>> On 8/16/07, Eric Firing <[EMAIL PROTECTED]> wrote:
>>>>>> Fernando,
>>>>>>
>>>>>> Thanks for taking the opportunity of checking into this now.  I
>>>>>> have to pass the buck, though--the bug you ran into looks like the
>>>>>> intersection between Mike's extensive mathtext work and Darren's
>>>>>> experimental replacement rc system, and apart from the testing you
>>>>>> refer to (prior to much of Mike's work) I have not dealt with
>>>>>> either of these areas.
>>>>> OK, understood.  No worries.
>>>>>
>>>>> I'm rebuilding to SVN from August 1st, which is when this
>>>>> conversation started.  That might do the trick and let us work here. 
>>>>> I'll pester again for help if I get stuck.
>>>> Eric is correct. I have to run in a minute, but I'll update the config
>>>> module early this evening to include Mikes recent changes.
>>> Fixed in svn 3711. gotta run!
>> Mmh, I'm afraid not:
> 
> Sorry, it should be fixed now. backend_driver.py runs all tests without any 
> failures for me, using svn 3713. Here are my results on my computer at home, 
> with the traited config disabled:
> 
> Backend Agg took 1.82 minutes to complete
>         template ratio 1.417, template residual 0.537
> Backend PS took 1.64 minutes to complete
>         template ratio 1.275, template residual 0.355
> Backend Template took 1.29 minutes to complete
>         template ratio 1.000, template residual 0.000
> Backend SVG took 1.69 minutes to complete
>         template ratio 1.313, template residual 0.403
> 
> and with the traited config enabled:
> 
> Backend Agg took 1.98 minutes to complete
>         template ratio 1.412, template residual 0.578
> Backend PS took 1.95 minutes to complete
>         template ratio 1.388, template residual 0.545
> Backend Template took 1.41 minutes to complete
>         template ratio 1.000, template residual 0.000
> Backend SVG took 1.72 minutes to complete
>         template ratio 1.226, template residual 0.318
> 
> That doesnt look too bad, compared to Eric's results. This is using a fresh 
> traits installation, installed today with:
> 
> sudo easy_install -f \ 
> http://code.enthought.com/enstaller/eggs/source "enthought.traits < 3.0a"
> 
> I dont know where to get the new eggs.
> 
> 
> I also tested it on my computer at work, which is 64bit, 4 processors, lots 
> of 
> ram, and SATA disks. Here are the results with traited config disabled:
> 
> Backend Agg took 0.99 minutes to complete
>         template ratio 1.639, template residual 0.386
> Backend PS took 0.82 minutes to complete
>         template ratio 1.364, template residual 0.220
> Backend Template took 0.60 minutes to complete
>         template ratio 1.000, template residual 0.000
> Backend SVG took 0.77 minutes to complete
>         template ratio 1.273, template residual 0.165
> 
> Here are the results with traited config enabled:
> 
> Backend Agg took 1.10 minutes to complete
>         template ratio 1.463, template residual 0.346
> Backend PS took 0.97 minutes to complete
>         template ratio 1.297, template residual 0.222
> Backend Template took 0.75 minutes to complete
>         template ratio 1.000, template residual 0.000
> Backend SVG took 0.91 minutes to complete
>         template ratio 1.220, template residual 0.165
> 

So, 10% slower with backend_agg, 18% slower with backend_svg.  It's not 
devastating, but it's not so great, either.

> Those results look fine to me. I dont know what has changed since we last 
> discussed this, but when Eric brought up the speed issue I remember the 
> traited config was significantly slower at that time. Maybe this is very good 
> news!
> 
Maybe there is some sensitivity to machine architecture; my tests were 
on a Lenovo T60 laptop, Core2 at 2 GHz.

For Fernando's simple_plot, using /usr/bin/time, I get:
0.53user 0.11system 0:00.66elapsed without traits
0.66user 0.21system 0:00.89elapsed with traits

(The figures are quite repeatable; numbers above are representative. CPU 
is 98% in both cases.)

So the total time for this very simple plot (which makes it something of 
a worst case) is more than 30% longer with traits than without, implying 
that the startup time increase is even larger as a percentage.  One 
might argue that the difference of 0.23 seconds doesn't matter, but I 
think it is still worth considering.  Maybe it can be beaten down to a 
small fraction of that.

Other major chunks of the startup time are simply importing numpy and 
pylab.  I don't know how much improvement is possible; maybe not much. 
I have already killed the biggest single contribution I could find, 
which was generation of the global FontManager instance.  Now it is read 
from a pickle.

Eric

> Darren


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Reply via email to