| This post was kindly contributed by Blogging about all things SAS - go there to comment and to read the full post. |
Finally got a chance to setup workspace pooling in SAS 9.1 and WRS 3.1.
Followed the instructions I outlined in this post
http://blog.saasinct.com/2010/09/28/speeding-up-web-report-studio-9-13-1-by-jumping-in-puddles/
Was simple enough to setup and get working, only trick was to remember to stop and restart the webserver so WRS/WRV could pick up the changes and switch over from load balanced to pooled.
Other issue was deciding what the minimum number of connections for a puddle to define. Checked the help, and there was some, but not a lot of insight was gained after reading it.
“Minimum Available Servers
Minimum Available Serversspecifies the minimum number of servers that should be idle and available in the pool at any time. The number of running servers never exceeds the Maximum Clients value specified on the server. If the number of available servers falls below the value specified in this field, additional server connections are created.Minimum Number of Serversspecifies the minimum number of servers (both idle and active) that should be present in the pool at any time. This value also specifies how many servers should be started when the pool is first created.”
Clear as mud eh!
But the key seems to be if you dont have enough pooled sessions available the users waits for one to become free. So you would create lots then wouldn’t you. Ah but each one is taking up memory as it sits there waiting for a request, so you dont want to many.
Haven’t found any form of management or monitoring tool that keeps track of how many sessions you have available and how many requests over time, and of course any mismatch. Im guessing we are going to have to go log mining yet again.
Some other good sources of info on Pools, Puddles, Sessions and Gumboots can be found here:
Planning the Pooling Security (IOM Bridge only)
| This post was kindly contributed by Blogging about all things SAS - go there to comment and to read the full post. |