[
https://issues.apache.org/jira/browse/LIBCLOUD-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15805153#comment-15805153
]
ASF subversion and git services commented on LIBCLOUD-826:
----------------------------------------------------------
Commit 03575ecfd9ac13a64c9469be87c96b1677de8493 in libcloud's branch
refs/heads/trunk from [~supertom]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=03575ec ]
[google compute] Improve performance of list nodes by caching volume
information.
We leverage the aggregated disk call and store the result. For the list node
operation, we've added an extra parameter to use the cached data, which results
to true.
Tests and fixtures updated as well.
Closes #813
Closes LIBCLOUD-826
Signed-off-by: Eric Johnson <[email protected]>
> GCE list nodes performance improvement
> --------------------------------------
>
> Key: LIBCLOUD-826
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-826
> Project: Libcloud
> Issue Type: Improvement
> Components: Compute
> Reporter: Tom Melendez
> Labels: gce
>
> list_nodes currently makes at least one independent API call to the disks/get
> API (to obtain disk information) for each node in the list. This change will
> use the disks/aggregatedList API for this instead, reducing NUM_INSTANCES API
> calls to one.
> I ran some simple command-line tests to demonstrate the improvements in
> response time and API calls.
> Below is an in-network comparison using 40 nodes in 4 different regions.
> ||Code||instances/zones/regions||Time (sec)||API Calls
> |Current 1.0|40/4/2|6.805|43|
> |with disks/aggregatedList|40/4/2|0.919|4|
> I have a PR forthcoming to implement this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
