Cron-based replication uses differences in file lists of the source and the target Artifactory to determine and replicate artifacts that the target does not have.
Artifactory 6.13.0 introduced a performance improvement for Cron-based replication but may require tuning up new parameter for the Cron-based replication. With this change, Artifactory will save the file list from the target to the filesystem, under the Artifactory temp work directory, as a file called FullTree-{timestamp}.json.gz. It is stored in memory while the list is populated in chunks then stored as compressed (gzipped) to conserve disk space, so even if the file list API returns 1GB, it would be saved as 100MB or less.
This file will be deleted after the replication is done or after the VM shuts down (in cases of shutting down mid-replications)
It may take a considerable amount of storage space if several cron-based replications run at the same time for repositories with a large number of artifacts and folders stored.