[issue12655] Expose sched.h functions

[Benjamin Peterson]

Benjamin Peterson <benjamin at python.org> added the comment:

2011/7/30 Charles-François Natali <report at bugs.python.org>:
>
> Charles-François Natali <neologix at free.fr> added the comment:
>
>> I actually implemented this because I wanted to confine a Python process to a cpu to prevent keep it from being tossed from core to core. It made sense to bring the other scheduling functions along for the ride.
>
> Why didn't you use something like:
>
> $ taskset <cpu mask> python myscript.py

Because I didn't want to type that every time I ran the script.

>
> By the way, binding a multi-threaded Python process to a single core
> is often a simple way to improve performance, because with the GIL the
> threads are actually serialized, so you have almost no contention, and
> your threads get hot cache.

Indeed, that's what I was doing.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue12655>
_______________________________________