[
https://issues.apache.org/jira/browse/JCLOUDS-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13818756#comment-13818756
]
Eli Polonsky edited comment on JCLOUDS-357 at 11/11/13 7:49 AM:
----------------------------------------------------------------
I will definitely try this. Thanks!
but dont you think a feature like i mentioned is worth having?
think of this: jclouds.NodeMetaData.location = false, would leave the location
field null for the VirtualGuestToNodeMeta conversion. you can also have it
apply to nested fields like:
jclouds.NodeMetaData.location.id = false.
So basically a simple implementation would be to define an interface that
includes methods for all populate fields actions and call each method based on
these properties.
Only this is that i am not sure how this fits exactly into the current design.
But this feature should be very useful, it gives the users much more
flexibility to different kind of environments without having to compile any
code.
was (Author: iliapolo):
I will definitely try this.
but dont you think a feature like i mentioned is worth having?
this of this: jclouds.NodeMetaData.location = false, would leave the location
field null for the VirtualGuestToNodeMeta conversion. you can also have it
apply to nested fields like:
jclouds.NodeMetaData.location.id = false.
So basically a simple implementation would be to define an interface that
includes methods for all populate fields actions and call each method based on
these properties.
Only this is that i am not sure how this fits exactly into the current design.
But this feature should be very useful, it gives the users much more
flexibility to different kind of environments without having to compile any
code.
> 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
(v6.1#6144)
