Endpoint Central server performance depends on hardware sizing, network configuration, routine maintenance, and database tuning. Follow these best practices to prevent slowdowns, timeouts, and instability. Each section covers a key area with recommended actions and reference documentation.
Deploy to the recommended specs for your endpoint count. Adequate CPU, memory, and disk handle peak activities — patch deployment, scans, and reporting. Insufficient hardware leads to throttling, memory paging, and database instability. For more details, kindly refer this article System requirements
Set bandwidth throttling, download policies, and distribution rules. Schedule large downloads and limit unnecessary connections to avoid latency and congestion across distributed environments. For more details, kindly refer this article Network settings guide
Schedule database cleanup, index optimization, log management, and backups. Automated cleanup prevents bloat, fragmented indexes, and potential data corruption over time. For more details, kindly refer this article Server maintenance guide
Review query execution, indexing, and connection pooling settings for PostgreSQL regularly. Poor tuning causes table scans, high disk I/O, and timeouts that destabilize the system. For more details, kindly refer this article Database optimization guide
When using Microsoft SQL Server, grant the VIEW SERVER STATE permission to the Endpoint Central database user. This enables visibility into query stats, wait states, and I/O metrics — supporting proactive monitoring, deadlock detection, and faster bottleneck resolution.
