If you are experiencing performance issues with your JetPatch console or aiming to boost its efficiency, this article provides a comprehensive guide to troubleshooting and optimization.
Important Note: If any of these steps require a change request window, please initiate one, and proceed with the remaining steps in the meantime:
- Are you running the at least the latest UR of N-1 JetPatch version (currently 4.2.6.X) (how to check and upgrade)?
- Is your environment sized properly?
- Have you optimized the DB?
- Are you running the recommended version of Postgres? 16.X recommended (how to check and upgrade)
- Are you running the recommended version of NGINX? 1.26.X recommended (how to check and upgrade)
-
Modify Advanced Settings
- Modify server polling interval (s) (40 sec default)
- show server as disconnected after (m) (15 min default)
- max-allowed-concurrent-operations (175 default)
-
All other advanced settings we should as default (see article)
-
Note: Increasing the value of either polling interval (seconds) or disconnect timeout (minutes), will improve performance (specifically CPU usage and number of HTTP hits)
Environment Size Polling Interval (Seconds) Disconnect Timeout (Minutes) Max Concurrent Operations (Range) Micro (up to 1K) 40 15 175 Small (up to 3K) 40-80 15-20 175-250 Medium (up to 8K) 80-160 20-30 250-350 Large (up to 13K) 160-320 30-50 350-525 X-Large (up to 20K) 320-520 50-80 525-775
-
Note: Increasing the value of either polling interval (seconds) or disconnect timeout (minutes), will improve performance (specifically CPU usage and number of HTTP hits)
- If there is still a problem, then we can look into a couple more items
- Intigua.properties (compare settings against a new env running the same version)
- Database (DB) maintenance
- If there is still a problem, then gather and share the following logs and files:
Comments
0 comments
Please sign in to leave a comment.