Problem

Deployment of containers could take lot of hours if there is already hundred of container synchronized.

For example, to deploy the 3000 containers by package of 300 containers.

1) Deployment of the first 300 containers :
./mapProxyDeployer DEPLOY /opt/tmp/MAPS_FR_PPR/MAPS_0001_to_0300/ -update -ignoreDate
./mapProxyDeployer FORCE_SYNC -update -ignoreDate
FORCE_SYNC started at 16h03 and finished at 16h38 :
It takes 35 minutes to synchronise the 300 containers from "deploy" to "cache".

2) Deployment of the next 300 containers :
./mapProxyDeployer DEPLOY /opt/tmp/MAPS_FR_PPR/MAPS_0301_to_0600/ -update -ignoreDate
./mapProxyDeployer FORCE_SYNC -update -ignoreDate
FORCE_SYNC started at 16h39 and finished at 17h45 :
It takes 66 minutes to synchronise the next 300 containers from "deploy" to "cache".

If you deploy 300 other containers it will take more than 66 minutes, at least 2 hours.
To deploy 3000 containers it takes more than 24 hours.

Resolution

Old containers must be cleaned regularly with /Interchange/tools :
./mapProxyDeployer
With "CLEAN_OLD" parameter

Removes containers with old versions of objects from Map Proxy.
Will permanently delete the database entries for CACHE or REJECT locations and the related folders stored on the filesystem.
Will also move the containers from autodeploy folder to a backup location.
Please note that the container may have valid versions of objects along with the deprecated objects.
FORCE_SYNC must be run to broadcast the change to all configured Integrator instances.