BMC Helix Mid Tier performance benchmark configuration settings
The following tables describe the Mid Tier configuration settings that were used.
Mid Tier JVM settings (tomcat startup.sh)
Settings |
|---|
-XX:+UseCompressedOops |
-XX:+UseConcMarkSweepGC |
-XX:MetaspaceSize=512m |
-XX:MaxMetaspaceSize=512m |
-Xms6144m |
-Xmx6144m |
-XX:NewRatio=2 |
-XX:+HeapDumpOnOutOfMemoryError |
-XX:+DisableExplicitGC |
Apache Tomcat settings (server.xml)
Parameter | Value | Unit |
|---|---|---|
Accept Count | 250 | — |
Max Threads | 2000 | — |
Connection Timeout | 60,000 | milliseconds |
Keep Alive Timeout | 60,000 | milliseconds |
Max Keep Alive Requests | 5,000 | — |
Min Spare Threads | 50 | — |
Mid Tier configuration settings (config.properties under ../midtier/WEB-INF/classes)
Key/value | Comments | Per tenant? | |
|---|---|---|---|
1 | arsystem.pooling_max_connections_per_server=350 | Maximum number of connections that MidTier will open to each Platform server on the Platform server list; generally, for casual users, a ratio of 1:4. | No. Provided that each tenant in the cluster supporting same workload. |
2 | arsystem.formhtmljs_expiry_interval=86400 | Browser cache directive interval for AR forms and activelinks. | Yes |
3 | arsystem.resource_expiry_interval=86400 | Browser cache directive for web resources (images, CSS, and so on) coming from Mid Tier. This value should match the value of the previous key for ease of maintenance. | Yes |
4 | arsystem.log_level=Severe | Log only the minimum. Can change to Info if more logging is needed for debugging. | No |
5 | arsystem.log_category=INTERNAL | Log only internal errors. Can add more categories if more logging is needed for debugging. | No |
6 | arsystem.use_loadbalanceinterval=true arsystem.use_loadbalanceinterval_limit=15 | — | No |
7 | arsystem.securitytoken_enable=false | Disabled for automation scripts | No |