News for hackers. Stuff that matters.
Re:On mutex performance and WTF::Lock by dom0 on Sunday April 02, 2017 @12:21PM (#14017666)
Starvation and similar problems have plagued software using locks for a long time. A prominent example which is well documented may be the various problems of the GIL implementation when certain workloads are applied (easiest example is one I/O bound thread and one CPU bound thread, which is also a typical real world scenario - ouch!)

[It should be noted that it is commonly rejected that the GIL is a scheduler, acts like a scheduler or should be a proper scheduler; all of which are untrue. Many locks are used as schedulers as well, which is especially true for a lock that controls execution of any and all code.]

Re:On mutex performance and WTF::Lock by cat199 on Sunday April 02, 2017 @02:30PM (#14018302)
Which GIL are you talking about?
Re:On mutex performance and WTF::Lock by dom0 on Sunday April 02, 2017 @03:51PM (#14018687)
Sorry, I meant the Python GIL. Should've written that.