This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: test_subprocess is far too slow
Type: Stage:
Components: Library (Lib) Versions: Python 2.4
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: astrand Nosy List: anthonybaxter, astrand, georg.brandl, mwh, tim.peters
Priority: normal Keywords:

Created on 2005-02-17 11:10 by mwh, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (10)
msg24321 - (view) Author: Michael Hudson (mwh) (Python committer) Date: 2005-02-17 11:10
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
msg24322 - (view) Author: Peter Åstrand (astrand) * (Python committer) Date: 2005-02-17 11:50
Logged In: YES 

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. 
msg24323 - (view) Author: Michael Hudson (mwh) (Python committer) Date: 2005-02-17 12:09
Logged In: YES 

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

"$ time ./python ../Lib/test/ 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

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.
msg24324 - (view) Author: Anthony Baxter (anthonybaxter) (Python triager) Date: 2005-02-17 13:16
Logged In: YES 

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.
msg24325 - (view) Author: Tim Peters (tim.peters) * (Python committer) Date: 2005-02-17 15:13
Logged In: YES 

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.
msg24326 - (view) Author: Peter Åstrand (astrand) * (Python committer) Date: 2005-02-17 15:17
Logged In: YES 

tim_one: test_subprocess only creates 65 processes on
Windows, compared to 1026 for UNIX. 
msg24327 - (view) Author: Peter Åstrand (astrand) * (Python committer) Date: 2005-03-03 20:53
Logged In: YES 

Fixed in HEAD revisions: 1.166

Fixed in 2.4 revisions:
msg24328 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2005-03-03 20:54
Logged In: YES 

Shouldn't it be closed then?
msg24329 - (view) Author: Peter Åstrand (astrand) * (Python committer) Date: 2005-03-03 20:58
Logged In: YES 

Forgot to close. 
msg24330 - (view) Author: Michael Hudson (mwh) (Python committer) Date: 2005-03-04 10:17
Logged In: YES 

Thank you!
Date User Action Args
2022-04-11 14:56:09adminsetgithub: 41590
2005-02-17 11:10:13mwhcreate