Heads Up! - Debian metadata calculation is based on a locking mechanism. Once a worker has started to index a specific combination of repository & distribution, another worker won’t start indexing another event for the same path while the lock exists. Increasing the workers’ allocation won’t help if all packages are deployed to the same repository and distribution.
The below-mentioned workers are part of the Artifactory async Thread Pool.
When changing the below configurations, you may need to consider increasing the total async Thread Pool.
Read more at: How do I tune Artifactory for heavy loads?
We will configure the mentioned properties in:
The below-mentioned workers are part of the Artifactory async Thread Pool.
When changing the below configurations, you may need to consider increasing the total async Thread Pool.
Read more at: How do I tune Artifactory for heavy loads?
We will configure the mentioned properties in:
$ARTIFACTORY_HOME/etc/artifactory.system.properties.Debian Local repository metadata calculation workers:
artifactory.debian.metadata.calculation.workers = 8Debian Virtual repository metadata calculation workers:
artifactory.debian.virtual.metadata.calculation.workers = 5Debian Cached Remote repository coordinates calculation workers:
artifactory.debian.coordinates.calculation.workers = 4