I really don't get some people here.
If this spinlock feature is slow it should be optimized, especially if windows is able to work faster with spinlocks, it should be obvious that there is headroom to improve.
What I really don't understand is people writting "I have 40 working threads on a quad core and everything is fine", where as this focuses on a single application which has multiple concurrent threads and works in realtime, which is a whole other type of problem, then having a few worker threads which for a non realtime problem...
Even if your problem is a realtime problem and has concurrent threads, the question still remains, is your scheduler a non-neglectable bottleneck. If it is, yes your problem is comparble, elsewise it isn't.
If this spinlock feature is slow it should be optimized, especially if windows is able to work faster with spinlocks, it should be obvious that there is headroom to improve.
What I really don't understand is people writting "I have 40 working threads on a quad core and everything is fine", where as this focuses on a single application which has multiple concurrent threads and works in realtime, which is a whole other type of problem, then having a few worker threads which for a non realtime problem...
Even if your problem is a realtime problem and has concurrent threads, the question still remains, is your scheduler a non-neglectable bottleneck. If it is, yes your problem is comparble, elsewise it isn't.
Comment