This documentation is for WSO2 Data Services Server 3.2.2. View documentation for the latest release.
Page Comparison - Performance Tuning (v.10 vs v.11) - Data Services Server 3.2.2 - WSO2 Documentation

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. To optimize network and OS performance, configure the following settings in /etc/sysctl.conf file of Linux. These settings specify a larger port range, a more effective TCP connection timeout value, and a number of other important parameters at the OS-level.

    Code Block
    net.ipv4.tcp_fin_timeout = 30 fs.file-max = 2097152 net.ipv4.tcp_tw_recycle = 1 net.ipv4.tcp_tw_reuse = 1 net.core.rmem_default = 524288 net.core.wmem_default = 524288 net.core.rmem_max = 67108864 net.core.wmem_max = 67108864 net.ipv4.tcp_rmem = 4096 87380 16777216 net.ipv4.tcp_wmem = 4096 65536 16777216 net.ipv4.ip_local_port_range = 1024 65535 
    Info

    When we have the localhost port range configuration lower bound to 1024, there is a possibility that some processes may pick the ports which are already used by WSO2 servers. Therefore, it's good to increase the lower bound as sufficient for production, e.g., 10,000.

  2. To alter the number of allowed open files for system users, configure the following settings in /etc/security/limits.conf file of Linux.

    Code Block
    * soft nofile 4096 * hard nofile 65535

    Optimal values for these parameters depend on the environment.

JVM Settings

 

If one or more worker nodes in a clustered deployment require access to the management console, you need to increase the entity expansion limit in the <DSS_HOME>/bin/wso2server.bat file (for windows) or the <DSS_HOME>/bin/wso2server.sh file (for Linux/Solaris) as show below. The default entity expansion limit is 64000.

 

Code Block
languagexml
-DentityExpansionLimit=100000

JDBC Pool Configuration

Within the WSO2 platform, we use Tomcat JDBC pooling as the default pooling framework due to its production ready stability and high performance. The goal of tuning the pool properties is to maintain a pool that is large enough to handle peak load without unnecessarily utilising resources. These pooling configurations can be tuned for your production server in general in the <DSS_HOME>/repository/conf/datasources/master-datasources.xml file, and for the RDBMS datasources created in your server:

...