Performance Tuning Recommendations

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.

WSO2 G-REG-level settings

Improvement Area	Performance Recommendations
Indexing Frequency	Change the value of the `<indexingFrequencyInSeconds>` element accordingly in the `<G-REG_HOME>/repository/conf/registry.xml` file. The default value is 3.
Zip Upload Thread Pool Size and Max File Upload Size	Change the value of the `SO_TIMEOUT` property to 7200000 in the `<G-REG_HOME>/repository/conf/axis2/axis2_client.xml` file, to increase the timeouts for the UI. Set the value of the `disableWSDLValidation` property to `false` in the `<G-REG_HOME>/repository/conf/registry.xml` file, to disable WSDL and Schema validation. Set the value of the `<startIndexing>` property to `false` in the `<G-REG_HOME>/repository/conf/registry.xml` file, to disable registry indexing. Set the value of the `<versionResourcesOnChange>` element to false in the `<G-REG_HOME>/repository/conf/registry.xml` file, to stop automatic versioning of resources. Set the number of maximum active DB connections to 120 and max_connection to 500 (MySQL level), and the maximum wait time to 600000 in the `<PRODUCT_HOME>/repository/conf/datasources/master-datasources.xml` file. Change the `Xmx` property in the `<PRODUCT_HOME>/bin/wso2server.sh` file (for Linux) or `<PRODUCT_HOME>/bin/wso2server.bat`et G-Reg memory configurations to 4GB.
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.
Memory Allocation	Increase memory allocated by modifying `/bin/wso2server.sh` with the following settings: -Xms16m -Xmx2048m -XX:MaxPermSize=1024m We recommend to keep `-Xms` as small as possible. E.g. `-Xms 16m` Governance Registry needs at least `192 Xmx` to start the Java instance, however `-Xmx` has to be enough for handle your workload. (Recommended allocation is `2048m` or more.) Governance Registry needs at least `128 MB` as `MaxPermSize`, to do basic operations like uploading ZIP file (with 23 WSDL).