ARTIFACTORY: How to debug and collect the information when Artifactory is slow or unstable
Artifactory UI Slowness:
Kindly refer to this Article make sure that the necessary tuning is done and in case of still facing the Artifactory UI Slowness we need to gather the below information:
- Clear the browser cookies, try in a different browser.
- Collect the HAR file by following the steps mentioned in this article.
- Artifactory support bundle.
Application slowness:
When facing the overall application slowness kindly gather the following information:
- Collect 10 thread dumps with intervals of 5 seconds, from each node in the cluster (3 nodes in the cluster).
https://jfrog.com/help/r/how-do-i-get-a-thread-dump/how-to-collect-artifactory-thread-dumps
3. There are spikes in CPU utilization
4. Network connectivity (proxy/firewall) issue.
5. Share the Artifactory Support bundle.
We can debug such scenarios where we are experiencing slowness issues with the Artifactory:The major reasons behind the slowness of the Artifactory could be:
Database:
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:
- Check whether there are high CPU spikes and the database is overloaded.
- 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.
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
Filestore
- Check if the filestore is not running out of disk space.
- If we are using an external filestore hosted in different instances, consider checking whether there is a network latency or connectivity issue due to which the Artifactory is taking more time to reach the filestore and serve the request.
Network
- If there are multiple layers introduced in between the Artifactory, database, and filestore there is a probability that we can experience some slowness in the Artifactory operations.
- Check the reverse-proxy setting whether it is blocking requests exceeding a certain amount of data.
Application
JVM Memory: Artifactory may run slowly if there is not enough memory allocated to it. The initial heap size (Xms) must be smaller than the maximum heap size (Xmx).