Re: [Matplotlib-users] speed up imports?

[Michael D. <md...@st...>]

It looks like most of the time is being taken up by pytz (timezone 
library), which opens ~500 files.  How does the total time of "import 
pytz" compare?

Mike

Andrew Kelly wrote:
> I see.  I was wondering why it spit out a binary file.
>
> test.out is attached...
>
> -Andy
>
> On Fri, Apr 2, 2010 at 10:55 AM, Michael Droettboom <md...@st... 
> <mailto:md...@st...>> wrote:
>
>     Can you provide the actual saved profiler data?  The output of the
>     command itself doesn't provide enough information to diagnose the
>     problem, since it doesn't have full file paths etc.
>
>     When you do (thanks Gökhan for the less verbose version):
>
>      python.exe -c "import cProfile; cProfile.run('import pylab',
>     'test.out')"
>
>     this should produce a binary file "test.out" that can be loaded
>     with the pstats module and used by GUI tools such as KCacheGrind
>     to help us get to the bottom of this.
>
>     Mike
>
>     Andrew Kelly wrote:
>
>         I'm back.
>
>         My backend is wx.  "Import wx" does not really take much time
>         to import at all.  In fact time.time() before and after = 0.0
>
>         Some computer details:
>         Processor: AMD Phenom IIx4 810 Processor 2.6 GHz
>         RAM: 8.00 GB
>
>         As for the cProfiler output on pylab, I have attached the
>         output as test.txt.
>          -Andy
>
>         On Fri, Apr 2, 2010 at 7:22 AM, Gökhan Sever
>         <gok...@gm... <mailto:gok...@gm...>
>         <mailto:gok...@gm... <mailto:gok...@gm...>>>
>         wrote:
>
>
>
>            On Fri, Apr 2, 2010 at 8:28 AM, Michael Droettboom
>            <md...@st... <mailto:md...@st...>
>         <mailto:md...@st... <mailto:md...@st...>>> wrote:
>
>                My gut says it's probably the GUI framework import that is
>                dominating
>                the time.  Which backend are you using?  Does importing it
>                take a large
>                amount of time as well?
>
>                Can you provide a profiler output file we can examine
>         to narrow it
>                down?  The following from a command prompt should be
>                sufficient to write
>                out a file called "import.prof":
>
>                 python.exe -c "import cProfile; prof=cProfile.Profile();
>                prof.run('import pylab', 'import.prof')"
>
>                Mike
>
>
>            Just for the records,
>
>            It reads as:
>
>            python -c "import cProfile; cProfile.run('import pylab',
>            filename='test.out')
>
>            in Python 2.6.2
>
>            These helped me to load the profile output:
>
>            import pstats
>            stats = pstats.Stats("test.out")
>            stats.print_stats()
>
>            --     Gökhan
>
>          
>          ------------------------------------------------------------------------------
>            Download Intel&#174; Parallel Studio Eval
>            Try the new software tools for yourself. Speed compiling,
>         find bugs
>            proactively, and fine-tune applications for parallel
>         performance.
>            See why Intel Parallel Studio got high marks during beta.
>            http://p.sf.net/sfu/intel-sw-dev
>            _______________________________________________
>            Matplotlib-users mailing list
>            Mat...@li...
>         <mailto:Mat...@li...>
>            <mailto:Mat...@li...
>         <mailto:Mat...@li...>>
>
>            https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>
>
>     -- 
>     Michael Droettboom
>     Science Software Branch
>     Operations and Engineering Division
>     Space Telescope Science Institute
>     Operated by AURA for NASA
>
>

-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA