News for hackers. Stuff that matters.
Re:Taking a Look at CLR Thread Pool 'Thread Injection' Algor... by obstinate on Thursday April 13, 2017 @08:02PM (#14111782)
We had a system like this at my workplace, but it is gradually being replaced with cooperative threads. I don't remember what specific issues we were having with it, but I believe slow adaptation to periodic workloads was one issue. Fundamentally, why hill climb when you can know with certainty exactly how many blocked threads there are in your system.
Re:Taking a Look at CLR Thread Pool 'Thread Injection' Algor... by ablankst on Friday April 14, 2017 @08:37AM (#14114082)
From [1] "in the case of blocking workloads, it’s extremely difficult to determine the number of threads that optimizes overall throughput because it’s hard to determine when a request will be completed." So the argument they make is that responding to the number of blocked threads directly could lead to an over-correction, where you add a lot of threads to the thread pool when threads are about to unblock. This reduces throughput because you now suffer context switches and poor cache locality.

[1] https://msdn.microsoft.com/en-us/magazine/ff960958.aspx

Re:Taking a Look at CLR Thread Pool 'Thread Injection' Algor... by obstinate on Friday April 14, 2017 @01:17PM (#14115663)
This is only a problem when you're not scheduling cooperatively. If you are scheduling cooperatively, then you don't ever have to experience unnecessary context switches.