This section describes some recommended performance tuning configurations to optimize App Manager. It assumes that you have set up App Manager on Unix/Linux, which are recommended for a production deployment. A distributed setup is also recommend for most production systems. Out of all components of an App Manager distributed setup, the API Gateway is the most critical, because it handles all inbound calls to APIs. Therefore, it is recommended to have at least a 2-node cluster of API Gateways in a distributed setup.
To optimize network and OS performance, configure the following settings in
/etc/sysctl.conffile 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.
It is not recommended to use
net.ipv4.tcp_tw_recycle = 1when working with network address translation (NAT), such as if you are deploying products in EC2 or any other environment configured with NAT.
To alter the number of allowed open files for system users, configure the following settings in
/etc/security/limits.conffile of Linux. (Be sure to include the leading * character).
Optimal values for these parameters depend on the environment.
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.conffile of Linux. (Be sure to include the leading * character). Each Carbon server instance you run would require upto 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).
If one or more worker nodes in a clustered deployment require access to the management console, you would need to increase the entity expansion limit as follows in the
<APPM_HOME>/bin/wso2server.bat file (for Windows) or the
<APPM_HOME>/bin/wso2server.sh file (for Linux/Solaris). The default entity expansion limit is 64000.