If an unusually heavy volume of requests are submitted to the SAS^® Stored Process Server, the server might, in some cases, use an excessive amount of memory.

For example, you might see this behavior when you perform a load test (stress test) using soapUI with 50 threads, where each thread submits 10 requests per second. In this scenario, the SAS Stored Process Server Current Server Cost might exceed the Maximum Cost, which results in too many requests running simultaneously on the SAS Sstored Process server.

If you encounter this behavior, these suggestions should be helpful.

• Consider adding more MultiBridge connections to your SAS Stored Process Server.

  Each MultiBridge connection is a separate SAS process that runs on your machine (and that listens on a specific port). So, if your machine has sufficient resources (especially memory and CPU capacity), it is helpful usually to add more MultiBridge connections to handle a heavy workload.

• Modify the load–balancing settings for your SAS Stored Process Server, as follows:
  1. Increase the Cost per client value. For example, increase this value from 1 (the default value) to 50.

     To increase the Cost per client value:

     1. Under Server Manager in SAS^® Management Console, select SASApp - Logical Stored Process Server ► Properties.
     2. In the Properties dialog box, click the Load Balancing tab. You can change the Cost per client value on this tab.
  2. Next, increase the Maximum Cost value for your SAS Stored Process Server. For example, if you increase the Cost per client to 50, then increase the Maximum Cost from the default value of 500 to 700.

     To increase the Maximum Cost value:

     1. Under Server Manager in SAS Management Console, select SASApp - Stored Process Server ► Properties ► Options ► Advanced Options.
     2. In the Advanced Options dialog box, click the Load Balancing tab. You can change the Maximum Cost value on this tab.
  3. Add the following logger element to your object spawner's logconfig.xml file:
     <logger name="IOM.LoadBalancing"> <level value="Trace"/> </logger>

     This logger element causes additional load-balancing logging information to be included in the object spawner's log file. For more information about logging for the SAS Object Spawner, see SAS Note 34893, "Turning on additional logging for the SAS Object Spawner."

  4. When you run your tests, follow these steps:
     1. Monitor the memory that is used by each SAS Stored Process Server process.
        • In Windows operating environments, use Windows Task Manager to monitor the memory use of each stored-process server process.
        • In UNIX operating environments, use the top command to monitor the memory use of each stored-process server process.
     2. Examine your object-spawner log file and check the COST= values for your SAS Stored Process Servers. These values are load-balancing costs.
     3. Examine your SAS Stored Process Server log file and check the COST= values for your SAS Stored Process Servers. These values are load-balancing costs.

        If you do not see these cost values in your SAS Stored Process Server log file, see SAS Note 34114, "Creating a detailed SAS^® Stored Process Server log by default" for information.

For more information about load balancing, see the following sections in the SAS^® 9.3 Intelligence Platform: Application Server Administration Guide:

• Understanding the Load-Balancing Algorithms
• Overview of Load Balancing

Operating System and Release Information

Product Family	Product	System	SAS Release
			Reported	Fixed*
SAS System	SAS Integration Technologies	Linux for x64	9.2 TS2M3
		Linux	9.2 TS2M3
		HP-UX IPF	9.2 TS2M3
		64-bit Enabled Solaris	9.2 TS2M3
		64-bit Enabled HP-UX	9.2 TS2M3
		64-bit Enabled AIX	9.2 TS2M3
		Windows Vista for x64	9.2 TS2M3
		Windows Vista	9.2 TS2M3
		Solaris for x64	9.2 TS2M3
		OpenVMS on HP Integrity	9.2 TS2M3
		Windows 7 Ultimate x64	9.2 TS2M3
		Windows 7 Ultimate 32 bit	9.2 TS2M3
		Windows 7 Professional x64	9.2 TS2M3
		Windows 7 Professional 32 bit	9.2 TS2M3
		Windows 7 Home Premium x64	9.2 TS2M3
		Windows 7 Home Premium 32 bit	9.2 TS2M3
		Windows 7 Enterprise x64	9.2 TS2M3
		Windows 7 Enterprise 32 bit	9.2 TS2M3
		Microsoft Windows XP Professional	9.2 TS2M3
		Microsoft Windows Server 2008 for x64	9.2 TS2M3
		Microsoft Windows Server 2008	9.2 TS2M3
		Microsoft Windows Server 2003 for x64	9.2 TS2M3
		Microsoft Windows Server 2003 Standard Edition	9.2 TS2M3
		Microsoft Windows Server 2003 Enterprise Edition	9.2 TS2M3
		Microsoft Windows Server 2003 Datacenter Edition	9.2 TS2M3
		Microsoft® Windows® for x64	9.2 TS2M3
		Microsoft Windows XP 64-bit Edition	9.2 TS2M3
		Microsoft Windows Server 2003 Enterprise 64-bit Edition	9.2 TS2M3
		Microsoft Windows Server 2003 Datacenter 64-bit Edition	9.2 TS2M3
		Microsoft® Windows® for 64-Bit Itanium-based Systems	9.2 TS2M3
		z/OS	9.2 TS2M3

* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.

---

The SAS Stored Process Server might use an excessive amount of memory when an unusually heavy volume of requests are submitted to the server.

Type:	Usage Note
Priority:

Date Modified:	2012-12-05 09:44:11
Date Created:	2012-11-07 12:32:12