Database:

ARTIFACTORY: How to debug and collect the information when Artifactory is slow or unstable

AuthorFullName__c
Shivani Budhodi
articleNumber
000005886
FirstPublishedDate
2023-10-12T15:52:36Z
lastModifiedDate
2025-07-22
VersionNumber
1
In order to avoid Artifactory slowness problems like slower response times for requests, dropped connections, connection pool depletion, timeouts, and node synchronization issues, it's crucial that Artifactory and the database have a stable and quick connection.

Things to consider checking:
  1. Check whether there are high CPU spikes and the database is overloaded.
  2. Number of open connections from the database to the Artifactory so that the database is not completely utilized and is able to handle the requests sent via Artifactory.
Generally, we will need a certain number of connections from the DB based on
Total # of connections = (number of nodes) * ((artifactory.database.maxOpenConnections * 2) + access.database.maxOpenConnections + metadata.database.maxOpenConnections) + 50;
3. Check whether the connectivity between the database and Artifactory is okay