This section describes some recommended performance tuning configurations to optimize the WSO2 Identity Server.
- Performance tuning requires you to modify important system files, which affect all programs running on the server. We recommend you to familiarize yourself with these files using Unix/Linux documentation before editing them.
- The parameter values we discuss below are just examples. They might not be the optimal values for the specific hardware configurations in your environment. We recommend you to carry out load tests on your environment to tune the IS accordingly.
When it comes to performance, the OS that the server runs plays an important role.
If you are running MacOS Sierra and experience long startup times for WSO2 products, try mapping your Mac hostname to 127.0.0.1 and ::1 in the
/etc/hosts file as described in this blog post.
Following are the configurations you can apply to optimize OS-level performance:
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).
Setting the thread execution limit for multitenant mode
In multitenant mode, the Carbon runtime limits the thread execution time. That is, if a thread is stuck or taking a long time to process, Carbon detects such threads, interrupts and stops them. Note that Carbon prints the current stack trace before interrupting the thread. This mechanism is implemented as an Apache Tomcat valve. Therefore, it should be configured in the
<PRODUCT_HOME>/repository/conf/tomcat/catalina-server.xml file as shown below.
classNameis the Java class name used for the implementation. This must be set to
thresholdgives the minimum duration in seconds after which a thread is considered stuck. Default value is 600 seconds.
JVM setting (Xmx) depends on your load. Given below are the general settings but if you are on a production environment, this might not be sufficent. In such situtaions, you can increase the load & tenancy.
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 limitattribute to the
<PRODUCT_HOME>/bin/wso2server.batfile (for Windows) or the
<PRODUCT_HOME>/bin/wso2server.shfile (for Linux/Solaris). The default entity expansion limit is 64000.
In a clustered environment, the entity expansion limit has no dependency on the number of worker nodes.
Database level settings
Set up the following database indexes in the Identity Server database to improve performance:
- create index
IDX_ITS_LMT on IDN_THRIFT_SESSION (LAST_MODIFIED_TIME);
- create index
IDX_IOAT_AT on IDN_OAUTH2_ACCESS_TOKEN (ACCESS_TOKEN);
If you want to remove unused tokens from the database, see Removing Unused Tokens from the Database.