Architecting, installing and maintaining your SAS environment

Stored Process Connections. How many is too many?

Reply
Frequent Contributor
Posts: 115

Stored Process Connections. How many is too many?

Hello,

We have several reports on the SAS portal which replaced a .net system. So these reports are very dynamic HTML heavy and run on stored processes.

Currently, I have 5 connection (the 3 original plus 2 more I added). I had to add 2 more because users were timing out waiting on a server.

This has help but I expect more users to come.

My question is regarding the number of connections I can add. How many is too many?

PROC Star
Posts: 392

Re: Stored Process Connections. How many is too many?

Hi,

Given that each multi-bridge connection, when the Stored Process Server is fully loaded, will result in a SAS process I think it boils down to how many SAS stored process server processes is appropriate for your expected load, your expected response time, and what your hardware can handle, giving consideration to what with other processes may also need to run on that machine (or set of machines).  There are a variety of tuning parameters that can be used to control load balanced servers and you also have the option to scale out with a load balanced cluster of multiple machines if necessary.  You can read more about it in the Overview of Load Balancing section in the SAS 9.3 Intelligence Platform: Application Server Administration Guide.

In your instance, 5 connections does not sound like too many (however I don't know the specs for your hardware and don't know what those stored processes are doing). There is an interesting discussion of stored process server load balancing and tuning parameters in SAS Usage Note 40567: Troubleshooting and tuning the SAS® Stored Process Server and SAS Pooled Works... Whilst this usage note relates to a SAS Marketing Automation situation, it does mention "... At least 9 is recommended ..." and "... if you have defined 40 Multibridge Stored Process Server connections..." so this might give you some examples of the numbers that have been used by others.

You could also try to set up a test environment, with a variety of multi-bridge connections and tuning parameters, run a simulated load of expected stored processes and find the sweet spot for response times. In the past I have used Apache JMeter as software to generate a simulated concurrent client load for a SAS Stored Process Server.

I hope this helps.

Cheers

Paul

Occasional Contributor
Posts: 9

Re: Stored Process Connections. How many is too many?

hi Jenny ,

can you share your experience of adding multiple connections , as in my environment i want to increase from  9 to 30 connection to my store process server .And i had good system configuration .

Thanks & Regards,

Satish

Occasional Contributor
Posts: 11

Re: Stored Process Connections. How many is too many?

[ Edited ]

It is recommended in this 2012 paper (Qing Ye, Richard Nardin, Romon Williams) to have up to 5 Multibridge connections (ports) per CPU core - http://support.sas.com/resources/papers/proceedings12/378-2012.pdf

 

Each Multibridge connection can handle up to 5 concurrent client requests, but you can configure it to process just one - http://support.sas.com/kb/57/180.html

 

I guess a lot also depends on how 'heavy' you expect those sessions to be.  If your dynamic html is being generated directly with SAS, you might consider alternative approaches, such as serving HTML / javascript directly from the web server and only calling SAS when data is needed.  The Boemska Data Adaptor is great for this, and it's use explained in more detail here - http://rawsas.blogspot.co.uk/2015/12/building-web-apps-with-sas.html

Ask a Question
Discussion stats
  • 3 replies
  • 804 views
  • 5 likes
  • 4 in conversation