[
https://issues.apache.org/jira/browse/CLOUDSTACK-4529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752106#comment-13752106
]
ASF subversion and git services commented on CLOUDSTACK-4529:
-------------------------------------------------------------
Commit 85507c236663379e06ee0ccf7e17ccb4991f4a99 in branch refs/heads/4.2 from
[~kelveny]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=85507c2 ]
CLOUDSTACK-4464,CLOUDSTACK-4529: use property collector to collect all
information in one round, we have a few other places that need to do it the
same way
(cherry picked from commit 4c6ec5f3c63cb486566d9260e77d2f21c79d9c07)
Signed-off-by: animesh <anim...@apache.org>
> VM internal name should not be retrived seperatly inside a loop, this will
> cause big performance impact
> -------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4529
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4529
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Kelven Yang
> Assignee: Kelven Yang
> Priority: Critical
>
> When I reviewed some of recent VMware changes, found that the latest change
> on HostMO.getVmVncPortsOnHost has introduced a performance impact.
> VMware API is designed to use as less as calls to vCenter with property
> collectors, we need to use it the right way to avoid individual call to
> vCenter, especially inside a loop
--
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
