cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chiradeep Vittal <Chiradeep.Vit...@citrix.com>
Subject Re: Job-Executor workers
Date Thu, 04 Apr 2013 18:53:39 GMT
Note that each deployment to local storage has to download the base
template to local disk from secondary storage. How big is the template?
How fast is your secondary storage?


On 4/4/13 11:36 AM, "Jeronimo Garcia" <garciaj.uk@gmail.com> wrote:

>Hi List.
>
>I'm having issues when deploying a big number of virtual machines across a
>number of nodes.
>
>the imporession that i get ( from the logs) is that the AsyncJobExecutor
>is
>pulling jobs from the queue and do them one by one (which when you are
>deploying a big number of virtual machines could take a long while)
>
>In AsyncJobManager.java i see something that could change this behaviour
>but im not sure:
>
>*final int cloudMaxActive =
>Integer.parseInt(dbProps.getProperty("db.cloud.maxActive"));
>                       *
>*int poolSize = (cloudMaxActive * 2) / 3;*
>
>.
>
>I'm using 'random' as vm.allocation.algorithm , and my rest is to deploy
>200 vms across 7 nodes using local storage, also im using
>cloud-server-4.0.1-1 version.
>
>I've tried playing with worker settings in agents and manager but i don't
>see any change so far.
>
>Thanks!


Mime
View raw message