Application Performance and Maintenance KBs

Application Performance and Maintenance KBs

Alert
The intention of this KB is to proactively take steps to mitigate performance issues and maintain application stability and health. It is vital to ensure that these instructions are followed when performing health checkups regularly for customers to improve sustainability of the application and mitigate performance issues, especially while handling support issues. If followed in a dedicated manner, can help reduce the turnaround time from the moment a performance issue is observed at customer end and extract the RCA sooner. This documents behaves as an index towards all Performance related instructions and guides.
Kindly reach out in case of any concerns or feedback.

1. General Maintenance
  1. Java Tuning
  2. Recording of CPU and Memory Statistics
  3. DB Maintenance Enabling and Operations Involved
  4. Performance Settings Thresholds
  5. AV Exclusion

2. Performance Logging and Collection
Warning
Kindly note that any log collection must be done over the copy of the log. Please copy the respective log(s), and then compress the copy to maintain integrity of the files. The compressed logs can be provided for analysis. This is to ensure all files are complete and remain intact.
3. Postgres Database
  1. Proactive PG Corruption Handling for Customer Tickets
  2. Safe PGSQL folder Collection
  3. External PG Requirements
  4. PG Configuration Tuning

4. SQL Server Database
  1. Read Committed Snapshot Isolation (RCSI)
  2. Maximum Degree of Parallelism (MAXDOP) Tuning
  3. Cost Threshold for Parallelism (CTFP) Tuning
  4. SQL Server Maximum Memory Configuration
  5. Manual Steps to Reindex and Update Statistics
  6. Procedure to enable View Server State Permission
  7. Procedure to install sp_WhoIsActive Utility
  8. Procedure to shrink Transaction Log
  9. File Auto-growth Configuration
  10. High CPU Consuming Query Statistics

5. Data Maintenance

WarningKindly note that any maintenance activity or cleanup schedule is advised to be run during downtime, i.e., off-hours. This is to minimize disruption to users and ensure optimal performance. Performing these tasks during peak usage times can lead to slower response times, errors, and even application unavailability for users. 
  1. Data Deletion and Archiving
  2. System Generated Notification Deletion
  3. Cleanup Schedules:
    1. Recent Items
    2. ErrorLog by Limit
    3. ACC Session by Limit
    4. SDPJobsinfo Table Cleanup (Fix)
    5. Audit History: Enabled from Admin -> Schedule Scan Page
    6. Trashed Requests Cleanup: ESM Portal -> Application Settings -> Timeframe for deleting trashed requests (days)
    7. Request Notification Cleanup: ESM Portal -> General Settings -> Remove System Notifications for closed requests completed within (timeframe)

6. Load Simulation and Testing
  1. Load Setup Sizing Guide
    1. Bundled Postgres Default Build
    2. SQL Server Default Build
  2. Configurations and Specifications Used in Load Setup
    1. Application Server Specifications
    2. Postgres Configuration
    3. SQL Server Specifications


Info
These will be maintained up to date regularly and information on any other required areas will be included in the future. In case of any recommendations, please contact the G3-SPS Team.