Comments by essence (Top 2 by date)

essence 5-Feb-13 19:42pm View

So I just confirmed that when using QueuedTaskScheduler the value of "Current Queue Length" in Performance Monitor shows permanently higher than zero.
In this case, I used a maximum concurrency of 8 and the "Current Queue Length" never dropped below 24. Curiously enough, in my test, I statically included the class, but I never actually queued any tasks!

essence 5-Feb-13 19:21pm View

I used QueuedTaskScheduler and it looks like it's very good.
But it seemed strange to me. Also, when implemented, I saw that it reserved threads as if it was its own thread pool. Then reguardless of running or not, the "Current Queue Length" was permanently raised when reviewing Performance Monitor. :(
I will try again using it. But the next thing I wanted was if the incoming flow of tasks reaches a limit, put the queuing thread on hold until there is enough slots to allow it. Otherwise you could progressively run out of memory depending on what your are trying to do.

Thank you very much for your response.