jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ignasi Barrera (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:26:18 GMT

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

Ignasi Barrera commented on JCLOUDS-357:

In my opinion that would add unnecessary complexity to the whole idea of transforming from
the provider model to the portable one. How many fields (and nested fields) could an object
have? Maintaining such a thing will be quite complex and a potential source of bugs: properties
have to be added/removed every time the model changes, they have to be renamed if a field
is renamed. What about people with existing properties in that case? If a field is renamed
code won't compile, and the change to do to existing software is just obvious. If using the
properties, code will silently break until someone figures out the old property is no longer
taking effect.

I think this approach would add a complexity and introduce several corner cases we shouldn't
have to deal with. Even more when there is an existing way to provide a custom transformation
function when needed.

> 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