How many concurrent threads will SRS 1.0 sp2 spin up to handle concurrent subscriptions? Is the alogrythm documented anywhere? It appears that changing the MaxQueueThreads from zero(Default Value) should have an impact on the number of threads. If so are there any MSFT best practices around changing this setting?
Thanks
If MaxQueueThreads = 0, SSRS will spin up as many threads as it thinks it needs to process all the subscriptions -- but I've never seen (internally or externally) this decision making process documented.
There also is no "patterns and practices" type guidance on changing this value...that being said, lots of small reports generally do better with a higher number here (so we can run multiple, quickly completing reports at the same time), while large reports like a smaller value (because we can run fewer big reports at the same time without RAM contention issues, I guess).
I played around with some "subscription tuning" scenarios a while back...You an read about what I learned here:
http://blogs.msdn.com/bimusings/archive/2005/08/17/452865.aspx
|||
After a little research, it looks like the main inputs into MaxQueueSettings are # CPUs and amount of free RAM...Thinking more about this, I suppose you could just use perfmon and watch the number of threads reportserverservice.exe and/or w3wp.exe spins up during heavy subscription activity along with RAM they utilize...then play with MaxQueueSettings
No comments:
Post a Comment