Koushik Das 8cf48ed2ce 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. Conflicts: server/src/com/cloud/deploy/DeploymentPlanningManagerImpl.java		2013-08-09 16:57:21 +05:30
..
DataCenterDeployment.java	api_refactor: refactor project apis	2012-12-03 22:10:32 -08:00
DeployDestination.java	committing Chip Childers patches fixing licensing headers	2012-06-12 12:32:58 -04:00
DeploymentClusterPlanner.java	Changed VirtualMachineProfile to be non-generic. From here on VirtualMachineManager will only manage vm instance. It doesn't understand the difference between different types of VMs. This makes the vmsync code to be generic across all vms.	2013-07-22 11:48:11 -07:00
DeploymentPlan.java	committing Chip Childers patches fixing licensing headers	2012-06-12 12:32:58 -04:00
DeploymentPlanner.java	CLOUDSTACK-4179: [Performance Testing] Time taken for Deploy VM async job to complete is considerably higher	2013-08-09 16:57:21 +05:30