[ python-Bugs-1124637 ] test_subprocess is far too slow

SourceForge.net noreply at sourceforge.net
Thu Feb 17 16:13:31 CET 2005


Bugs item #1124637, was opened at 2005-02-17 06:10
Message generated for change (Comment added) made by tim_one
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1124637&group_id=5470

Category: Python Library
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Michael Hudson (mwh)
Assigned to: Peter Åstrand (astrand)
Summary: test_subprocess is far too slow

Initial Comment:
test_subprocess takes multiple minutes.  I'm pretty
sure it's "test_no_leaking".  It should either be sped
up or only tested when some -u argument is passed to
regrtest.

----------------------------------------------------------------------

>Comment By: Tim Peters (tim_one)
Date: 2005-02-17 10:13

Message:
Logged In: YES 
user_id=31435

Peculiar -- test_subprocess takes about 8 seconds on my 
WinXP box release build, about 10 seconds debug build, and 
Windows is notorious for slow process creation.  That's a 
zippy 3.4 GHz P4, but clock rate alone can't account for such 
a large speed difference.

----------------------------------------------------------------------

Comment By: Anthony Baxter (anthonybaxter)
Date: 2005-02-17 08:16

Message:
Logged In: YES 
user_id=29957

I'm with mwh. This test should be enabled with an option -
I'd noticed that test_subprocess took a long time, but
hadn't bothered to track it down.

Before releases (and at other times) I always try to make
sure that I run 'make testall', but for day-to-day use, this
is too slow.


----------------------------------------------------------------------

Comment By: Michael Hudson (mwh)
Date: 2005-02-17 07:09

Message:
Logged In: YES 
user_id=6656

Bog standard linux pc -- p3 933, 384 megs of ram.

"$ time ./python ../Lib/test/regrtest.py test_subprocess"
reports 2 minutes 7.  This is a debug build, a release build
might be quicker.  A run of the entire test suite takes a
hair over nine minutes, so 20-odd % of the time seems to be
test_subprocess.

It also takes ages on my old-ish ibook (600 Mhz G3, also 384
megs of ram), but that's at home and I can't time it.

----------------------------------------------------------------------

Comment By: Peter Åstrand (astrand)
Date: 2005-02-17 06:50

Message:
Logged In: YES 
user_id=344921

Tell me a bit about your type of OS and hardware. On my
machine (P4 2.66 GHz with Linux), the test takes 28 seconds. 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1124637&group_id=5470


More information about the Python-bugs-list mailing list