[
https://issues.apache.org/jira/browse/CLOUDSTACK-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547639#comment-13547639
]
Koushik Das commented on CLOUDSTACK-596:
----------------------------------------
Applied in master, pl. close the review;
CLOUDSTACK-596 : DeployVM command takes a lot of time to return job id Issue
happens...
authorKoushik Das <[email protected]>
Mon, 10 Dec 2012 08:26:51 +0000 (13:26 +0530)
committerAbhinandan Prateek <[email protected]>
Mon, 10 Dec 2012 09:32:53 +0000 (14:32 +0530)
commit238c55fb6e40220cbbf60b241a902cdc7ccf8d37
> DeployVM command takes a lot of time to return job id
> -----------------------------------------------------
>
> Key: CLOUDSTACK-596
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-596
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: pre-4.0.0, 4.0.0
> Reporter: Koushik Das
> Assignee: Koushik Das
> Fix For: 4.1.0
>
>
> This is a perf issue typically seen for larger deployments (advanced zone,
> user accounts ~4k, lot of guest networks). The issue happens when deployVM is
> called without 'networkids' parameter. In this case a search is done to
> identify the default guest network to use for deploying VM. The search logic
> doesn't scale up for larger deployments resulting in delay in returning async
> job id.
> Tests results showed that for ~4k user accounts and similar number of guest
> networks it takes approx. 15 secs. to return async job id.
--
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
