[Python-Dev] Issue #10348: concurrent.futures doesn't work on BSD (original) (raw)
Victor Stinner victor.stinner at haypocalc.com
Wed Dec 29 23:55:48 CET 2010
- Previous message: [Python-Dev] Issue #10348: concurrent.futures doesn't work on BSD
- Next message: [Python-Dev] Issue #10348: concurrent.futures doesn't work on BSD
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Le mercredi 29 décembre 2010 à 21:49 +0100, "Martin v. Löwis" a écrit :
Of course, one may wonder why testfirstcompleted manages to create 41 SemLock objects, when all it tries to do is two future calls.
More numbers (on Linux):
- Queue: 3 SemLock
- Condition: 4 SemLock
- Event: 5 SemLock
- Call (test_concurrent_futures): 10 SemLock (2 Event)
- ProcessPoolExecutor: 11 SemLock (2 Queue, 1 Condition)
FreeBSD 7.2 is limited to 30 semaphores, so with ProcessPoolExecutor, you can only create one Call object, whereas some tests use 4 Call objects or more.
Victor
- Previous message: [Python-Dev] Issue #10348: concurrent.futures doesn't work on BSD
- Next message: [Python-Dev] Issue #10348: concurrent.futures doesn't work on BSD
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]