[jira] [Commented] (CLOUDSTACK-4529) VM internal name should not be retrived seperatly inside a loop, this will cause big performance impact

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-4529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751791#comment-13751791 ] 

ASF subversion and git services commented on CLOUDSTACK-4529:
-------------------------------------------------------------

Commit 687e87faa7a2d828fa428ac0b013e0c1de361bdc in branch refs/heads/4.2-forward from [~kelveny]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=687e87f ]

CLOUDSTACK-4529: use property collector to collect all information in one round

                
> 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