Message365263
Also, adding `p.join()` immediately after `p.start()` in my sample code showed this timing:
```
$ time python3.8 multi1.py
worker 0 done, got 100 numbers
worker 1 done, got 0 numbers
worker 2 done, got 0 numbers
worker 3 done, got 0 numbers
real 0m2.342s
user 0m0.227s
sys 0m0.111s
$
```
Setting instead start to `fork` showed this timing:
```
$ time python3.8 multi1.py
worker 2 done, got 25 numbers
worker 0 done, got 25 numbers
worker 1 done, got 25 numbers
worker 3 done, got 25 numbers
real 0m0.537s
user 0m0.064s
sys 0m0.040s
$
```
The proposed fix is roughly four times slower, compared to reverting start to `fork`. |
|
Date |
User |
Action |
Args |
2020-03-29 15:34:58 | mouse07410 | set | recipients:
+ mouse07410, barry, gregory.p.smith, ronaldoussoren, mark.dickinson, pitrou, vstinner, ned.deily, lukasz.langa, josh.r, tdsmith, davin, Ryan May, pablogsal, miss-islington, kapilt |
2020-03-29 15:34:58 | mouse07410 | set | messageid: <1585496098.39.0.0229469686974.issue33725@roundup.psfhosted.org> |
2020-03-29 15:34:58 | mouse07410 | link | issue33725 messages |
2020-03-29 15:34:58 | mouse07410 | create | |
|