You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Adrian Cole (JIRA)" <ji...@apache.org> on 2011/04/18 16:12:05 UTC

[jira] [Issue Comment Edited] (WHIRR-61) make more efficient use of ComputeServiceContext

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

Adrian Cole edited comment on WHIRR-61 at 4/18/11 2:11 PM:
-----------------------------------------------------------

@andrei the largest startup time is parsing images, locations, and hardware profiles in the cloud.  This is a function of the response time of the rest requests from the server, which vary dramatically from 150ms -> 30 seconds (image fetch in amazon).  jclouds optimizes this as much as possible.  blobstore context startup only saves a couple seconds or less, as the only thing parsed there are locations (ex. getBucketLocation in s3).

      was (Author: adrian@jclouds.org):
    @andrei startup is referring to the time to parse the images, locations, and hardware profiles in the cloud.  I've seen this take 30 seconds in amazon, probably a few to several seconds in other clouds.  optimizing blobstore context startup only saves a couple seconds or less, I suspect, as the only thing parsed there are locations.
  
> make more efficient use of ComputeServiceContext
> ------------------------------------------------
>
>                 Key: WHIRR-61
>                 URL: https://issues.apache.org/jira/browse/WHIRR-61
>             Project: Whirr
>          Issue Type: Improvement
>            Reporter: Adrian Cole
>
> The ComputeService object is thread-safe, and better off shared inside the Service object.  Regardless, it must be closed in order to release threadpools.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira