jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Polonsky (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-357) ComputeService.listnodes() in the case of softlayer cloud takes about 2 minutes for cloud with only 3 machines
Date Mon, 11 Nov 2013 08:44:17 GMT

    [ https://issues.apache.org/jira/browse/JCLOUDS-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13818775#comment-13818775

Eli Polonsky commented on JCLOUDS-357:

I understand what you are saying. and this is definitely not an easy feature to have...but
i do have some counters to a few of the things you mentioned.

though unfortunately i probably wont have time to get into this now anyway. but is there an
official place i can raise a feature request and we can have some discussion on it?

Also, i am trying to use the code you mentioned. Can you explain what is does? is it actually
replacing the implementation of the VirtualGuestToNodeMetaData class to my own? how can you
bind a class to something and not an interface? should my CustomFunction extend VirtualGuestToNodeMetaData,
or should it implement Function<VirtualGuest, NodeMetadata>?

thanks so much.

> ComputeService.listnodes() in the case of softlayer cloud takes about 2 minutes for cloud
with only 3 machines
> --------------------------------------------------------------------------------------------------------------
>                 Key: JCLOUDS-357
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-357
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-compute
>    Affects Versions: 1.5.10, 1.6.2
>         Environment: Windows 7 64-bit
>            Reporter: Evgeny Fisher
>            Priority: Critical
>              Labels: softlayer
> The significant delay is on the following call: method apply(VirtualGuest) of 
> org.jclouds.softlayer.compute.functions.VirtualGuestToNodeMetadata 
>  findLocationForVirtualGuest.apply(from).
> If I removes in above calling initializing location within builder then it improves performance
dramatically: instead of 2 minutes it takes now about 12 seconds in order to bring 3 nodes..
> Performance is improved as well if in addition to location the following fields of builder
are not initialized: operatingSystem, hardware, group.
> I think initializing of of these builder fields should be optional, since like in my
case I need only id, hostname, public IP and private ip.
> I'm aware that next calls will go to cache and will have much better performance, but
I need good performance already during first call.

This message was sent by Atlassian JIRA

View raw message