BMC Digital Workplace Catalog Server performance configuration settings
This topic contains the following information:
BMC Digital Workplace Catalog Server configuration settings
The following tables describe the BMC Digital Workplace Catalog server configuration settings:
BMC Digital Workplace Catalog server configuration settings (ar.conf)
Parameter and value | Comments |
---|---|
Max-Entries-Per-Query: 2,000 | None |
Allow-Unqual-Queries: T | None |
Cache-Mode: 0 | Disable development cache mode |
CMDB-Service-Suspended: T | None |
Full-Text-Mode: Disabled | None |
Max-Database-Connections: 400 | Default |
BMC Digital Workplace Catalog server thread settings (ar.conf)
Parameter and value | Number of threads (port number minimum/maximum) | Comments |
---|---|---|
Private-RPC-Socket: 390601 | 1/1 | Alert queue |
Private-RPC-Socket: 390603 | 1/1 | Escalation queue |
Private-RPC-Socket: 390620 | 8/12 | Fast queue |
Private-RPC-Socket: 390635 | 8/20 | List queue |
Private-RPC-Socket: 390680 | 2/2 | Approval queue |
Jetty Server Configuration (jetty.xml)
Parameter | Value | Comments |
---|---|---|
maxThreads | 200 | Maximum Threads |
minThreads | 10 | Minimum Threads |
BMC Digital Workplace Catalog Server Java virtual machine (JVM) settings
The following table contains JVM settings for the BMC Digital Workplace Catalog server
JVM Settings (arserverd.conf)
Paramters | Value | Comments |
---|---|---|
jvm.minimum.heap.size | 6442450944 | JVM minimum heap size |
jvm.maximum.heap.size | 6442450944 | JVM maximum heap size |
JVM options |
---|
-XX:+UseCompressedOops |
-XX:+UseConcMarkSweepGC |
-XX:+UseParNewGC |
-XX:MetaspaceSize=256M |
-XX:MaxMetaspaceSize=512M |
-XX:NewRatio=2 |
Jetty maxThreads and Max-Database-Connections Configuration
Below are the recommendations for Jetty maxThreads and Max-Database-Connections
- Based on the internal lab testing, recommended ratio of Jetty maxthreads and Max-Database-Connections should be 1:1. i.e. 200 Jetty 'maxThreads' and 200 'Max-Database-Connections' as default.
- If there are any custom API’s which are spawning 2 to 3 database connections per API which can be monitored using netstat and ‘Max-Database-Connections' parameter value can be tuned accordingly.
- Jetty maxthreads value should be kept in the range of 200 to 500. One should start with default of 200 and if required, increase to higher limits gradually by monitoring application but not exceeding to 500. Unnecessary setting the jetty maxThreads to upper limit can led to performance issues.