cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kelven Yang (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CLOUDSTACK-4529) VM internal name should not be retrived seperatly inside a loop, this will cause big performance impact
Date Tue, 27 Aug 2013 22:15:52 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kelven Yang reassigned CLOUDSTACK-4529:
---------------------------------------

    Assignee: Kelven Yang
    
> 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

Mime
View raw message