libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LIBCLOUD-826) GCE list nodes performance improvement
Date Fri, 06 Jan 2017 18:04:58 GMT

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

ASF GitHub Bot commented on LIBCLOUD-826:
-----------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/libcloud/pull/813


> 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)

Mime
View raw message