Re:BrainFuck inspired scheduler successfully replaced the Py...
by kinghajj on Friday March 26, 2010 @01:09AM
(#1220316)
If he's fixed the bugs and gotten it to be portable (at least to POSIX), then why shouldn't it get adopted? Just look at those benchmark results! 259ms per loop instead of the next best of 1.25s. If a real app gets improvements from this, it should be a no-brainer.
[ Parent
| on HN ]
Re:BrainFuck inspired scheduler successfully replaced the Py...
by mbreese on Friday March 26, 2010 @01:20AM
(#1220326)
I'd wait to see how this works with a real workload as opposed to his contrived example. It looks like it might be good, but it definitely needs to be better tested.
Re:BrainFuck inspired scheduler successfully replaced the Py...
by sid0 on Friday March 26, 2010 @03:39AM
(#1220499)
Glancing at the patch, it looks like it should work on both POSIX and Win32.
Re:BrainFuck inspired scheduler successfully replaced the Py...
by JoachimSchipper on Friday March 26, 2010 @05:44AM
(#1220627)
At least the patch as first proposed suffered from all-the-world-is-Linux (see the discussion of CLOCK_THREAD_CPUTIME_ID)...
Re:BrainFuck inspired scheduler successfully replaced the Py...
by rbanffy on Friday March 26, 2010 @06:19AM
(#1220669)
You have to start with one platform. You then make it work on the others.
If I write something that initially only runs on IRIX and then make it work on other OSs, it would be unfair to attribute it an all-the-world-is-IRIX. It just happens the guy had a Linux box to refine his idea to the point of working, unfortunately using stuff other OSs don't offer in the same way.