You might want to implement one or more of the following tuning suggestions if you are encountering performance issues while running SIP servlets.
The following recommendations are provided as is without any implied warranty.
To make these changes, in the administrative console, click Servers > Server Types > WebSphere application servers > server_name > Java and Process Management > Process Definition > Java Virtual Machine.
To make these changes, in the administrative console, click Servers > Server Types > WebSphere application servers > server_name > Java and Process Management > Process Definition > Control > Java Virtual Machine.
To make these changes, in the administrative console, click Servers > Server Types > WebSphere application servers > server_name > Java and Process Management > Process Definition > Logging and Tracing > JVM Logs.
To make these changes, in the administrative console, click Servers > Server Types > WebSphere application servers > server_name > Java and Process Management > Process Definition > Control > Logging and Tracing > JVM Logs.
These setting changes enable the JVM to detect if the operating system has hung.
To make these changes, in the administrative console, click Servers > Server Types > WebSphere application servers > server_name > Java and Process Management > MonitoringPolicy.
To make these changes, in the administrative console, click Servers > Server Types > WebSphere application servers > server_name > SIP Container Settings > sip_container.
Name | Value |
---|---|
javax.sip.max.object.pool.size | 1000 |
javax.sip.stat.report.interval | 0 |
max.tu.pool.size | 1000 |
weight.overload.watermark | 1 |
end.of.service.replication | true |
immediate.replication | false |
thread.message.queue.max.size | 5000 |
bootstrap.batch.size | 1000 |
bootstrap.blocking.delay | 500 |
Name | Value |
---|---|
sendBufferSizeSocket | 3000000 |
receiveBufferSizeSocket | 3000000 |
To make these changes, in the administrative console, click Servers > Server Types > Proxy servers > proxy_server_name > Proxy server settings.
To add these ports, click Ports on the Proxy servers > proxy_server_name page.
To add these properties, from the Proxy server settings page, click SIP proxy settings > Custom Properties.
Name | Value |
---|---|
isSipComplianceEnabled | false |
serverUDPInterface | The host name of the network that is handling SIP traffic for the proxy server. This value becomes the Container Facing Interface. |
serverUDPPort | 5080 This port becomes the Container Facing Port. |
LBIPAddr | The Load Balancer IP address. This address is not the cluster address. |
SIPAdvisorMethodName | Options |
maxThroughputFactor | 90 |
perSecondBurstFactor | 200 |
burstResetFactor | 120 |
sipProxyStartupDelay | 120000 |
proxyTransitionPeriod | 360 |
minDeflatorRatio | 6 |
maxDeflatorRatio | 10 |
keepAliveInterval | 2000 |
keepAliveFailures | 3 |
clusterRouteConfigUpdateDelay | 60000 |
localOutboundTCPAddress | The IP address of the local outbound TCP connection |
localOutboundTCPPort | The port number of the local outboud TCP connection |
receiveBufferSizeSocket | 3000000 |
sendBufferSizeSocket | 3000000 |
To delete the UDP transport chain UDP_SIP_PROXY_CHAIN, click SIP proxy server settings > SIP proxy server transports on the Proxy server settings page, select the UDP transport chain UDP_SIP_PROXY_CHAIN, and then click Delete.
To change the settings of the SIP proxy server transport, click SIP proxy server settings > SIP proxy server transports > New on the Proxy servers > proxy_server_name page, and then specify the following settings for the new transport:
To change the settings of the SIP proxy server transport, click SIP proxy server settings > HTTP proxy server transports > New on the Proxy servers > proxy_server_name page, and then specify the following settings for the new transport:
To add new custom properties to the UDP channel settings, click SIP proxy transport chains > UDPInboundChannel > Custom Properties > New on the SIP proxy server settings page.
Name | Value |
---|---|
sendBufferSizeSocket | 3000000 |
receiveBufferSizeSocket | 3000000 |
To add this property, click Proxy server settings > Proxy settings > Custom Properties > New on the Proxy servers > proxy_server_name page.
Name | Description | Value |
---|---|---|
localOutboundTCPAddress | Local outbound interface address | The proxy address of the network that is handling SIP traffic. |
localOutboundTCPPort | 1080 | Local outbound port |
To make these changes, in the administrative console, click Servers > Server Types > WebSphere proxy servers > proxy_server_name > Java and Process Management > Process Definition > Java virtual machine.
To make these changes, in the administrative console, click Servers > Server Types > WebSphere proxy servers > proxy_server_name > Java and Process Management > Process Definition > Control > Java virtual machine.
If you are running over 50 proxy servers in your environment, you might also want to specify –Xmo200m to –Xmo600m
To make these changes, in the administrative console, click Servers > Server Types > WebSphere proxy servers > proxy_server_name > Java and Process Management > Process Definition > Logging and Tracing > JVM Logs.
To make these changes, in the administrative console, click Servers > Server Types > WebSphere proxy servers > proxy_server_name > Java and Process Management > Process Definition > Control > Logging and Tracing > JVM Logs.
To add this property, click Administration > Custom Properties > New on the Proxy servers > proxy_server_name page. Then specify IBM_CLUSTER_RUNRULES_TIMER_TIME in the Name field, and 1000 in the Value field.
For the application server, in the administrative console, click Servers > Server Types > WebSphere application servers > server_name, and enter 100 for the Transport buffer size property.
For the proxy server, in the administrative console, click Servers > Server Types > WebSphere proxy servers > server_name, and enter 100 for the Transport buffer size property.
In the administrative console, click System administration > Deployment manager > Core group service, and enter 100 for the Transport buffer size property.
In the administrative console, click System administration > Node agents > node_agent Core group service, and enter 100 for the Transport buffer size property.
Name | Description | Value |
---|---|---|
IBM_CS_FD_PERIOD_SECS | This custom property specifies, in seconds, how frequently the Failure Detection Protocol checks the core group network connections that the discovery protocol establishes. The Failure Detection Protocol notifies the Discovery Protocol if a connection failure occurs. | 2 |
IBM_CS_FD_CONSECUTIVE_MISSED | This custom property specifies the consecutive
number of heartbeats that must be missed before the core group member
is considered failed. Do not configure this custom property unless you are running in a mixed cell environment that includes at least one core group that contains a mixture of Version 7.0 and Version 6.x processes. |
3 |
IBM_CS_DATASTACK_MEG | This custom property specifies, in megabytes,
the amount of memory that is available for synchronization. Do not configure this custom property unless you are running in a mixed cell environment that includes at least one core group that contains a mixture of Version 7.0 and Version 6.x processes. |
100 |
In this information ...Related reference
| IBM Redbooks, demos, education, and more(Index) Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience. This feature requires Internet access. Most of the following links will take you to information that is not part of the formal product documentation and is provided "as is." Some of these links go to non-IBM Web sites and are provided for your convenience only and do not in any manner serve as an endorsement by IBM of those Web sites, the material thereon, or the owner thereof. |