Benjamin Peterson <benja...@python.org> added the comment: 2011/7/30 Charles-François Natali <rep...@bugs.python.org>: > > Charles-François Natali <neolo...@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 <rep...@bugs.python.org> <http://bugs.python.org/issue12655> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
