JVM Memory Allocation
While not a strict requirement, we recommend that you modify the JVM memory parameters used to run Artifactory.
You should reserve at least 512MB for Artifactory, and the recommended values for JVM parameters are as follows:
Recommended JVM parameters:
The larger your repository or number of concurrent users, the larger you need to make the -Xms and -Xmx values accordingly.
Recommended values are:
Artifactory has been tested with the latest versions of Google Chrome, Firefox, Microsoft Edge and Safari. (Note that since January 2016, Microsoft does not provide security updates or technical support for Internet Explorer, so this browser is not officially supported by Artifactory).
The following table provides hardware recommendations for a single server machine:
|Number of developers||OS/JVM||Processor||*Memory (RAM) for JVM Heap||Storage|
|1 - 20||64 bit||4 cores||4GB||Fast disk with free space that is at least 3 times the total size of stored artifacts|
|20 - 100||64 bit||4 cores||8GB||Fast disk with free space that is at least 3 times the total size of stored artifacts|
|100 - 200||64 bit||8 cores (16 cores recommended)||12GB||Fast disk with free space that is at least 3 times the total size of stored artifacts (backup SAN recommended)|
|200+||64 bit||Please contact JFrog support for a recommended setup.|
*Memory (RAM) for JVM Heap
This specifies the amount of memory that Artifactory requires from the JVM heap. The server machine should have enough additional memory to run the operating system and any other processes running on the machine.
For the purposes of this table, a build machine is considered equivalent to 10 developers
Working with Very Large Storage
In most cases, our recommendation is for storage that is at least 3 times the total size of stored artifacts in order to accommodate system backups. However, when working with a very large volume of artifacts, the recommendation may vary greatly according to the specific setup of your system.
Therefore, when working with over 10 Tb of stored artifacts, please contact JFrog support who will work with you to provide a recommendation for storage that is customized to your specific setup.
High Availability Configuration
If you are running Artifactory in a High Availability configuration, to maintain high system performance in case of single or multiple server crash, we recommend following the recommended hardware guidelines above for each of the HA server instances. For more details, please refer to Artifactory High Availability.
To avoid network latency issues when reading and writing artifacts data, we strongly recommend creating the database either on a machine that is network close (latency well below 1 ms) to the machine on which Artifactory is running (database engine and storage) with fast storage. This recommendation is critical when using fullDb (whereby files are served from database BLOBs) and the file system cache is small.
For supported databases and more details, please refer to Configuring the Database.
Artifactory should be run with its bundled Tomcat 8 servlet container.
From version 5.5, Artifactory is bundled with Tomcat version 8.5.23.