This section describes some recommended performance tuning configurations to optimize the API Manager. It assumes that you have set up the API Manager on Unix/Linux, which is recommended for a production deployment. We also recommend a distributed API Manager setup for most production systems. Out of all components of an API Manager distributed setup, the API Gateway is the most critical, because it handles all inbound calls to APIs. Therefore, we recommend you to have at least a 2-node cluster of API Gateways in a distributed setup.
The values we discuss below are only general recommendations for the API Gateway. They work best when there are 350 to 30000 calls per second to the API Gateway. They might not be the optimal for the specific hardware configurations in your environment. We recommend you to carry out load tests on your environment to tune the API Manager accordingly.
|Improvement Area||Performance Recommendations|
|API Gateway nodes|
Increase memory allocated by modifying
|NHTTP and PT HTTP transports of API Gateway|
Set the following in
Note that the number of threads should be equal to the number of processor cores .
|Key management nodes|
Apply the following to get the maximum outcome for login requests: