cloudstack/engine
Koushik Das 21c74c6453 CLOUDSTACK-4179: [Performance Testing] Time taken for Deploy VM async job to complete is considerably higher
The time increased due to the newly added dedicated resources feature. During regular VM deployment, all dedicated resources are put in avoid list so that they are not considered for deployment.
Now the way to compute the list of dedicated resources is not optimal and performance deteriorates in an environment having lot of pods, clusters and hosts as the logic is to query db. for each suc resource.

The fix is to optimize the logic not to loop through all resources but get the list of each resource type in a single query.
2013-08-09 16:03:17 +05:30
..
api CLOUDSTACK-3568: [Automation]Parallel deployment - Vmware - When 2013-08-07 11:13:56 -07:00
components-api Removing ^M's from code. 2013-04-04 00:53:20 +05:30
compute CLOUDSTACK-1317: Bump CloudStack package version to 4.2.0-SNAPSHOT in all poms 2013-02-20 16:42:56 +05:30
network CLOUDSTACK-1317: Bump CloudStack package version to 4.2.0-SNAPSHOT in all poms 2013-02-20 16:42:56 +05:30
orchestration CLOUDSTACK-3886: check in for review request https://reviews.apache.org/r/13008/ 2013-08-07 10:29:18 -07:00
planning/src/org/apache/cloudstack/platform/planning Added engine 2012-11-05 09:14:14 -08:00
schema CLOUDSTACK-4179: [Performance Testing] Time taken for Deploy VM async job to complete is considerably higher 2013-08-09 16:03:17 +05:30
service CLOUDSTACK-1317: Bump CloudStack package version to 4.2.0-SNAPSHOT in all poms 2013-02-20 16:42:56 +05:30
storage CLOUDSTACK-4133 2013-08-09 13:53:31 +05:30
pom.xml integration test is passed again 2013-05-12 14:41:06 -07:00