Page Comparison

...

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 time-out value, and a number of other important parameters at the OS-level.

   Info
   It is not recommended to use net.ipv4.tcp_tw_recycle = 1 when working with network address translation (NAT), such as if you are deploying products in EC2 or any other environment configured with NAT.

   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

2. To alter the number of allowed open files for system users, configure the following settings in /etc/security/limits.conf file of Linux (be sure to include the leading * character).

   Code Block
   * soft nofile 4096 * hard nofile 65535

   Optimal values for these parameters depend on the environment.

3. To alter the maximum number of processes your user is allowed to run at a given time, configure the following settings in  /etc/security/limits.conf file of Linux (be sure to include the leading * character). Each carbon server instance you run would require upto up to 1024 threads (with default thread pool configuration). Therefore, you need to increase the nproc value by 1024 per each carbon server (both hard and soft).

   Code Block
   * soft nproc 20000 * hard nproc 20000

...

• JVM heap size (Xmx) depends on your load. Given below are the general settings but if you are on a production environment, this might not be sufficent sufficient. In such situtaions situations, you can increase the heap size accordlingly accordingly.

  Code Block
  -Xms2048m -Xmx2048m

• When an XML element has a large number of sub-elements and the system tries to process all the sub-elements, the system can become unstable due to a memory overhead. This is a security risk.
  
  To avoid this issue, you can define a maximum level of entity substitutions that the XML parser allows in the system. You do this by adding the entity expansion limit attribute to the <PRODUCT_HOME>/bin/wso2server.bat file (for Windows) or the <PRODUCT_HOME>/bin/wso2server.sh file (for Linux/Solaris). The default entity expansion limit is 64000.

  Code Block
  -DentityExpansionLimit=100000

  In a clustered environment, the entity expansion limit has no dependency on the number of worker nodes.

...

Set up the THRIFT_SESSION database indexe index in the Identity Server database to improve performance:

...