[Matplotlib-devel] import time doubled by master vs 1.4.3

Eric Firing efiring at hawaii.edu
Tue Sep 8 22:53:07 CEST 2015


On 2015/09/08 9:51 AM, Thomas Caswell wrote:
> My guess is that this has to do with disk access?  With venvs running on
> a ramdisk I get almost identical times, particularly if I run it a
> couple of times:

I ran

strace python -c "from matplotlib import pyplot" > ../tests/master.trace 
2>&1
and similar for v1.4.3:

-rw-r--r-- 1 efiring efiring   448374 Sep  8 10:46 v143.trace
-rw-r--r-- 1 efiring efiring   774942 Sep  8 10:49 master.trace
(python3)efiring at manini4:~/work/programs/py/mpl/tests$ grep matplotlib 
master.trace | wc
     899    4988  127344
(python3)efiring at manini4:~/work/programs/py/mpl/tests$ grep matplotlib 
v143.trace | wc
     693    3890   99963
(python3)efiring at manini4:~/work/programs/py/mpl/tests$ grep stat 
master.trace | wc
    4307   27785  463042
(python3)efiring at manini4:~/work/programs/py/mpl/tests$ grep stat 
v143.trace | wc
    2381   14898  248260

Somehow, master seems to have nearly doubled the number of stat calls. 
Maybe there is more circularity in the imports now?

Eric





More information about the Matplotlib-devel mailing list