This note provides recommended c3p0.properties values for improving the performance and system stability of SAS Digital Marketing version 6.x.

The c3p0.properties are set for the SAS Digital Marketing Server, bess.war, and sdm.war servers. In release 6.3 and later, the properties for the SAS Digital Marketing Server are included in the c3p0.properties file in sdm.war.

For SAS^® Digital Marketing 6.1_M1:

For SAS Digital Marketing Server, the default c3p0 settings are as follows:

c3p0.acquireRetryDelay=1000
c3p0.numHelperThreads=4
c3p0.maxPoolSize=25
c3p0.acquireRetryAttempts=5
c3p0.acquireIncrement=1

For sdm.war and bess.war, the default c3p0 settings are as follows:

c3p0.acquireRetryDelay=1000
c3p0.numHelperThreads=4
c3p0.maxPoolSize=10
c3p0.acquireRetryAttempts=5
c3p0.acquireIncrement=1

For SAS^® Digital Marketing 6.3, 6.4 and 6.5

For sdm.war (which includes SAS Digital Marketing Server), the default c3p0 settings are as follows:

c3p0.acquireRetryDelay=1000
c3p0.numHelperThreads=4
c3p0.maxPoolSize=25
c3p0.acquireRetryAttempts=5
c3p0.acquireIncrement=1

For bess.war, the default c3p0 settings are as follows:

c3p0.acquireRetryDelay=1000
c3p0.numHelperThreads=4
c3p0.maxPoolSize=5
c3p0.acquireRetryAttempts=5
c3p0.acquireIncrement=1

For more information about an issue with setting the c3p0.properties in SAS Digital Marketing Server 6.1_M1, see SAS Note 54654, "Default and updated c3p0 properties are not honored for the SAS® Digital Marketing Server."

If you experience performance issues, set the c3p0 logging to review use, as described in SAS Note 54664 "Setting up logging for monitoring c3p0 use in SAS® Digital Marketing."

To improve the performance and stability of SAS Digital Marketing, consider updating the c3p0.properties file in line with the following advice:

Set c3p0.maxPoolSize using the following formulas:

• For SAS Digital Marketing 6.1_M1: (1) + (2) + (3) + (4) + some buffer on SAS Digital Marketing Server and (5) + some buffer on the sdm.war. For a high-volume system, you might end up with 50 to 65 c3p0.maxPoolSize connections.
• For SAS Digital Marketing 6.3, 6.4 and 6.5: (1) + (2) + (3) + (4) + (5) + some buffer. For a high-volume system, you might end up with 40 to 50 c3p0.maxPoolSize connections.

In these formulas:

• (1) represents the number of concurrent users of SAS^® Customer Intelligence Studio.
• (2) represents the number of parallel JDBC update threads; if enabled – the default number is 5 (if disabled, the default number is 1). See SAS Note 52978, "There might be a delay in updates to the SAS^® Digital Marketing tables and performance might be badly affected."
• (3) represents the number of CIExtension threads (the default number is 10 in SAS Digital Marketing 6.3. It is not concurrent in SAS Digital Marketing 6.1 and, therefore, is 1).
• (4) represents the number of connections that are required to publish content (web-publish). This is a big variable. If the publish requests are high, more c3p0 connections are required to achieve the desired performance.
• (5) represents the number of connections required for ebCIquery command in case of CIExtension. This is another variable. Consider the interval between SAS Customer Intelligence updates and the average number of broadcasts that are executed daily. Note that for a production system, the Advanced Server property CIModelRefreshInterval should not use the default setting of 600 seconds (10 minutes). Instead, you should use a value between 1 and several hours.

Set c3p0.numHelperThreads to 8, if either or more cores are available when you increase c3p0.maxPoolSize.

Monitor and increase memory allocation for the servers, as needed.

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
			Reported	Fixed*	Reported	Fixed*
SAS System	SAS Digital Marketing	Microsoft® Windows® for x64	6.1_M1		9.3 TS1M2
		Microsoft Windows 8 Enterprise 32-bit	6.1_M1		9.3 TS1M2
		Microsoft Windows 8 Enterprise x64	6.1_M1		9.3 TS1M2
		Microsoft Windows 8 Pro 32-bit	6.1_M1		9.3 TS1M2
		Microsoft Windows 8 Pro x64	6.1_M1		9.3 TS1M2
		Microsoft Windows 8.1 Enterprise 32-bit	6.1_M1		9.3 TS1M2
		Microsoft Windows 8.1 Enterprise x64	6.1_M1		9.3 TS1M2
		Microsoft Windows 8.1 Pro	6.1_M1		9.3 TS1M2
		Microsoft Windows 8.1 Pro 32-bit	6.1_M1		9.3 TS1M2
		Microsoft Windows Server 2003 Datacenter Edition	6.1_M1		9.3 TS1M2
		Microsoft Windows Server 2003 Enterprise Edition	6.1_M1		9.3 TS1M2
		Microsoft Windows Server 2003 Standard Edition	6.1_M1		9.3 TS1M2
		Microsoft Windows Server 2003 for x64	6.1_M1		9.3 TS1M2
		Microsoft Windows Server 2008	6.1_M1		9.3 TS1M2
		Microsoft Windows Server 2008 R2	6.1_M1		9.3 TS1M2
		Microsoft Windows Server 2008 for x64	6.1_M1		9.3 TS1M2
		Microsoft Windows Server 2012 Datacenter	6.1_M1		9.3 TS1M2
		Microsoft Windows Server 2012 R2 Datacenter	6.1_M1		9.3 TS1M2
		Microsoft Windows Server 2012 R2 Std	6.1_M1		9.3 TS1M2
		Microsoft Windows Server 2012 Std	6.1_M1		9.3 TS1M2
		Microsoft Windows XP Professional	6.1_M1		9.3 TS1M2
		Windows 7 Enterprise 32 bit	6.1_M1		9.3 TS1M2
		Windows 7 Enterprise x64	6.1_M1		9.3 TS1M2
		Windows 7 Home Premium 32 bit	6.1_M1		9.3 TS1M2
		Windows 7 Home Premium x64	6.1_M1		9.3 TS1M2
		Windows 7 Professional 32 bit	6.1_M1		9.3 TS1M2
		Windows 7 Professional x64	6.1_M1		9.3 TS1M2
		Windows 7 Ultimate 32 bit	6.1_M1		9.3 TS1M2
		Windows 7 Ultimate x64	6.1_M1		9.3 TS1M2
		Windows Vista	6.1_M1		9.3 TS1M2
		Windows Vista for x64	6.1_M1		9.3 TS1M2
		64-bit Enabled AIX	6.1_M1		9.3 TS1M2
		64-bit Enabled HP-UX	6.1_M1		9.3 TS1M2
		64-bit Enabled Solaris	6.1_M1		9.3 TS1M2
		HP-UX IPF	6.1_M1		9.3 TS1M2
		Linux for x64	6.1_M1		9.3 TS1M2
		Solaris for x64	6.1_M1		9.3 TS1M2

* 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.

---

Type:	Usage Note
Priority:

Date Modified:	2014-11-25 11:06:18
Date Created:	2014-11-19 06:19:34