Issue6269
Created on 2009-06-11 20:37 by segfaulthunter, last changed 2009-09-22 16:33 by illume.
| File name |
Uploaded |
Description |
Edit |
Remove |
|
threading.rst.patch
|
segfaulthunter,
2009-06-11 20:37
|
Add Note about GIL to threading.rst |
|
|
|
msg89259 - (view) |
Author: Florian Mayer (segfaulthunter) |
Date: 2009-06-11 20:37 |
|
I think the GIL should be mentioned in the threading documentation, so
that people do not try to use them for scalability reasons.
|
|
msg89838 - (view) |
Author: Jesse Noller (jnoller) |
Date: 2009-06-29 13:52 |
|
I strongly disagree with the wording of the patch as-is. It makes no
mention of the simple fact that I/O blocked threads get a benefit with
threading, and so on.
I do agree with adding some details about this in the core documentation
however.
|
|
msg93003 - (view) |
Author: Rene Dudfield (illume) |
Date: 2009-09-22 16:33 |
|
hello,
CPU intensive programs can also benefit from the GIL if they use code
which releases the GIL around the CPU intensive parts.
Some parts of python do this, as do the numpy and pygame extensions
amongst others.
Another good, but separate, documentation patch would be to document
which functions release the GIL.
cheers,
|
|
| Date |
User |
Action |
Args |
| 2009-09-22 16:33:30 | illume | set | nosy:
+ illume messages:
+ msg93003
|
| 2009-07-11 10:52:58 | georg.brandl | set | assignee: georg.brandl -> jnoller |
| 2009-06-29 13:52:09 | jnoller | set | nosy:
+ jnoller messages:
+ msg89838
|
| 2009-06-11 20:37:15 | segfaulthunter | create | |
|