PoolDiagnostics.jsp is a tool that is available with a hot fix for both SAS® Decision Services 5.5 M1 and 6.1. (See SAS Note 51957 "SAS Real-Time Decision Manager does not provide tuning information for pooled resources without a hot fix.") These releases are contained in SAS Real-Time Decision Manager 5.41 M1 and 5.6, respectively. This tool is also available without a hot fix in subsequent releases of SAS Decision Services (6.3 and 6.4) and SAS Real-Time Decision Manager (6.3 and 6.4). Note that due to security concerns, beginning with SAS Decision Services 6.4 M1 (SAS Real-Time Decision Manager 6.5), PoolDiagnostics.jsp is only available from SAS Professional Services.
SAS Decision Services uses pools of resources such as threads and database connections. The size and persistence parameters for these pools need to be configured in order to provide the best throughput. PoolDiagnostics.jsp is a web page on the SAS Decision Services Engine web application that displays the status of the primary thread pool and the JDBC Connection pools for that engine. Based on the data that is displayed, you can adjust the pool configuration for the best performance. Information on how to adjust the pool configuration is available in the SAS Decision Services Administrators Guide. This information is also available in the most recent version of the SAS Real-Time Decision Manager Administrators Guide.
There are two types of pools that the PoolDiagnostics.jsp page monitors.
For the SAS Federation Server, every connection from the engine creates a service thread that loads and compiles any DS2 packages that are called for execution on that thread. Once a DS2 package is loaded on a thread, it remains in that thread's memory until the connection is discarded. Loading and compiling DS2 packages is expensive because of the time to create each thread and compile code, as well as the memory that the thread and its compiled DS2 packages occupies. Initializing the thread pool to be large enough to accommodate this demand will increase performance for flows that use the SAS Federation Server. However, making the thread pool too large uses resources unnecessarily and, in some environments, can actually decrease performance or use memory unnecessarily.
For database connections, the size of the JDBC connection pool should be sized for the capacity and throughput of the database server that it is referencing. If there is insufficient capacity on the database server to accommodate more connections, increasing the connection pool size merely moves any I/O bottleneck to the database server. Although the increase in available connections moves the bottleneck from the engine, it does not improve the throughput unless the database's availability for connections is also increased.
The PoolDiagnostics.jsp page can be displayed using any browser that has access to the SAS Decision Services Engine web application. To see the PoolDiagnostics.jsp page, enter the following URL:
http://ip-address-of-engine-server:port-of-engine-web-application-server/RTDM/PoolDiagnostics.jsp
The page automatically refreshes every 5 minutes. If you prefer a different refresh frequency, use an appropriate value for the query parameter refreshSeconds. The following URL refreshes the page every two seconds:
http://ip-address-of-engine-server:port-of-engine-web-application-server/RTDM/PoolDiagnostics.jsp?refreshSeconds=2
Items Displayed
The following are displayed:
For each JDBC connection pool, the following information is displayed:
Product Family | Product | System | Product Release | SAS Release | ||
Reported | Fixed* | Reported | Fixed* | |||
SAS System | SAS Real-Time Decision Manager | Microsoft® Windows® for x64 | 5.4_M1 | 6.3 | 9.2 TS2M3 | 9.4 TS1M1 |
Microsoft Windows Server 2008 | 5.4_M1 | 6.3 | 9.2 TS2M3 | 9.4 TS1M1 | ||
Microsoft Windows Server 2008 R2 | 5.4_M1 | 6.3 | 9.2 TS2M3 | 9.4 TS1M1 | ||
Microsoft Windows Server 2008 for x64 | 5.4_M1 | 6.3 | 9.2 TS2M3 | 9.4 TS1M1 | ||
Windows 7 Enterprise 32 bit | 5.4_M1 | 6.3 | 9.2 TS2M3 | 9.4 TS1M1 | ||
Windows 7 Enterprise x64 | 5.4_M1 | 6.3 | 9.2 TS2M3 | 9.4 TS1M1 | ||
Windows 7 Home Premium 32 bit | 5.4_M1 | 6.3 | 9.2 TS2M3 | 9.4 TS1M1 | ||
Solaris for x64 | 5.4_M1 | 6.3 | 9.2 TS2M3 | 9.4 TS1M1 | ||
Linux for x64 | 5.4_M1 | 6.3 | 9.2 TS2M3 | 9.4 TS1M1 | ||
64-bit Enabled Solaris | 5.4_M1 | 6.3 | 9.2 TS2M3 | 9.4 TS1M1 | ||
64-bit Enabled AIX | 5.4_M1 | 6.3 | 9.2 TS2M3 | 9.4 TS1M1 | ||
Windows 7 Ultimate x64 | 5.4_M1 | 6.3 | 9.2 TS2M3 | 9.4 TS1M1 | ||
Windows 7 Ultimate 32 bit | 5.4_M1 | 6.3 | 9.2 TS2M3 | 9.4 TS1M1 | ||
Windows 7 Professional x64 | 5.4_M1 | 6.3 | 9.2 TS2M3 | 9.4 TS1M1 | ||
Windows 7 Professional 32 bit | 5.4_M1 | 6.3 | 9.2 TS2M3 | 9.4 TS1M1 | ||
Windows 7 Home Premium x64 | 5.4_M1 | 6.3 | 9.2 TS2M3 | 9.4 TS1M1 | ||
SAS System | SAS Decision Services | Solaris for x64 | 5.5 | 6.3 | 9.3 TS1M1 | 9.4 TS1M1 |
Linux for x64 | 5.5 | 6.3 | 9.3 TS1M1 | 9.4 TS1M1 | ||
HP-UX IPF | 5.5 | 6.3 | 9.3 TS1M1 | 9.4 TS1M1 | ||
Microsoft® Windows® for x64 | 5.5 | 6.3 | 9.3 TS1M1 | 9.4 TS1M1 | ||
64-bit Enabled AIX | 5.5 | 6.3 | 9.3 TS1M1 | 9.4 TS1M1 | ||
64-bit Enabled Solaris | 5.5 | 6.3 | 9.3 TS1M1 | 9.4 TS1M1 |
Type: | Usage Note |
Priority: | high |
Date Modified: | 2014-01-10 10:00:05 |
Date Created: | 2014-01-08 13:47:13 |