This section describes some recommended performance tuning configurations to optimize the Governance Registry. It assumes that you have set up the Governance Registry on Unix/Linux, which is recommended for a production deployment.
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, increase the entity expansion limit as follows in the
<G-REG_HOME>/bin/wso2server.bat file (for Windows) or the
<G-REG_HOME>/bin/wso2server.sh file (for Linux/Solaris). The default entity expansion limit is 64000.
WSO2 Carbon platform-level settings
In multi-tenant mode, the WSO2 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. 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.xmlfile as shown below.
classNameis the Java class used for the implementation. Set it to
thresholdgives the minimum duration in seconds after which a thread is considered stuck. The default value is 600 seconds.
<validationInterval>configurations accordingly which are related to database connections in the
- G-Reg server needs at least two database connections to startup the server. The recommended minimum database connection count is 8, the max active database count should be defined according to your requirements and the maximum database connection which can be handled with the database system.
- The value of the
<maxActive>element should be more than the value of the
<indexerPoolSize>element in the
|Improvement Area||Performance Recommendations|
|Indexing Frequency||Change the value of the |
|Zip Upload Thread Pool Size and Max File Upload Size|
|Solr - RAM Buffer||If you are loading a lot of data at once, then increase this value. A number in the vicinity of 128 is applicable for most apps.|
|Solr - Merge Factor||When the Merge Factor is low, the indexed document count is low.|
|Solr - Lock Timeouts|
Setting the Solr lock timeout value with a higher value indexes more documents at once and Solr response time is lower.
Our current Solr configuration is appropriate for most G-Reg related operation, except for huge file indexing.
Increase memory allocated by modifying