[ https://issues.jboss.org/browse/JBIDE-13283?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13283: ---------------------------------------- According to helpdesk, Akamai rule was set up for the jbosstools/static folder. I just run simultaneously resolution of the same TP, one linking to jbosstools/updates/requirements (No Akamai) and the other one to jbosstools/static/requirements (Akamai) and here are the results Each of these runs in using Kepler M6, a TP from commit 773a5a40012f06c057a44309235843b6cc670aff (pre-M7, pre-pack.gz), and is on a dedicated new workspace. No Akamai 1st run with updates/requirements: ~13m30s 2nd run with updates/requirements: ~10m30s Akamai 1st run with static/requirements: ~13m30s 2nd run with static/requirements: ~6m40s 3rd run with static/requirements: ~6m30s So Akamai cache mechanism can divide by 2 the time to resolve a Target Platform. Since it fully relies on p2, I'd bet it would divide by 2 installation times as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira