Hi, Le dimanche 16 mai 2010 22:07:06, Nir Aides a écrit : > *Evolving the GIL into a scheduler* > > The problem addressed by the GIL has always been *scheduling* threads to > the interpreter, not just controlling access to it. The patches by Antoine > and David essentially evolve the GIL into a scheduler, however both cause > thread starvation or high rate of context switching in some scenarios (see > data below).
I didn't followed last development around the GIL. Can you explain me why Python should have its own scheduler whereas each OS has already its own scheduler? The OS has useful informations to help scheduling that Python doesn't have. Linux and FreeBSD schedulers are faster each year since... 5 years?, especially with multiple CPU/cores. -- Victor Stinner http://www.haypocalc.com/ _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com