Tuning SAS Micro Analytic Service :: SAS(R) Micro Analytic Service 1.2: Programming and Administration Guide

Adjust Thread Pool Size

Tasks in SAS Micro Analytic Service, such as revision compilations and method executions, are performed by special worker threads, which are part of the SAS threaded kernel architecture. These worker threads are maintained in a thread pool. The size of the thread pool to use is provided to SAS Micro Analytic Service as a start-up parameter. By default, the thread pool size is set to 4. Optimum performance is usually achieved by setting the thread pool size about equal to the number of cores in the hosting server. However, the optimum setting might vary depending on the characteristics of the programs that are run by SAS Micro Analytic Service.

To change the worker thread pool size:

In SAS Management Console, expand Application Management.
Expand SAS Application Infrastructure.
Right-click SAS Micro Analytic Service 1.2.
Select Properties.
Click the Advanced tab.
Unlock masintf.tk.threads in the Property Name column.
Change the value. To tell SAS Micro Analytic Service to automatically set the worker thread pool size equal to the number of server cores, enter 0 (zero) for the value.
Click OK.

Adjust Serial or Parallel Content Creation

The POST operation on the modules collection and the PUT and DELETE operations on a module are serialized by default. They are taken in the order of arrival to the REST server's processing queue, one after another is done. To adjust this setting to allow them to be done in parallel:

In SAS Management Console, expand Application Management.
Expand SAS Application Infrastructure.
Right-click SAS Micro Analytic Service 1.2.
Select Properties.
Click the Advanced tab.
Unlock masintfc.tk.serializecontentcreation in the Property Name column.
Change the value. The choices are true and false. The default value is True.
Click OK.

Adjust DS2 Module Compilation Mode

The REST server always inserts a DS2 option in front of a DS2 module to force it to be compiled in SAS mode. You can stop this behavior by changing a property:

In SAS Management Console, expand Application Management.
Expand SAS Application Infrastructure.
Right-click SAS Micro Analytic Service 1.2.
Select Properties.
Click the Advanced tab.
Unlock masintfc.tk.sasmode in the Property Name column.
Change the value. The choices are true and false. The default value is true.
Click OK.

Increase Module ExecutionThroughput of the REST Interface

The module execution throughput of the SAS Micro Analytic Service REST interface can be increased. However, those making connections to the REST server to execute micro analytics must always be authorized and authenticated by some other means, such as a private network. If this is the case, you can edit the JVM option that starts the REST server to include the argument

 -Dsas.mas.access.mode=private

As a result, the authentication is not required to execute micro analytics. Authentication is still required for other operations.

As a result of specifying this option, the CPU cycles and sockets that are used for authentication are available for other uses, such as executing micro analytics.

The place to edit the JVM option is host specific:

Linux - SAS/config/LevN/Web/WebAppServer/SASServer13_X/bin/setenv.sh
Windows - SAS\Config\LevN\Web\WebAppServer\SASServer13_X\conf\wrapper.conf

Prevent HTTP Error Messages

To prevent HTTP error messages, make sure that the web server is located on a separate host machine from the web application server. When the web server and web application server are located on the same machine, they both compete to use the ephemeral ports on the system. Separating them reduces the contention for this finite resource.