What are good points of say, VMware nodes set up for good performance?

Also, what would you recommend for reaching 1hr?

On Wednesday, September 17, 2014 1:38:57 PM UTC-7, SA Evans wrote:
>
> Alex,
>
> The first question I'd ask is what part of the build is running at 100% 
> cpu, and can you tell what processes are consuming the cpu at that time?  
> You need to figure out the bottlenecks and where your pain points are 
> first, before trying to solve your performance issues (or perceived 
> issues).  If your build is doing a ton of CPU-intensive work that's all 
> legitimate, then I'd think your 1 hour goal is not realistic, given the 
> information you've provided and assuming you've already set up your VMware 
> nodes properly for good performance.
>
> Scott
>
> On Wed, Sep 17, 2014 at 3:24 PM, Alex Demitri <[email protected] 
> <javascript:>> wrote:
>
>> Hi! We just started using Jenkins for continuous intergration. The code 
>> is pulled from Perforce. We have one jenkins master (Windows VM) and 3 
>> slaves (Windows VMs). I am more the VMware admin than a programmer.
>>
>> I have been trying to tweak more and more the Jenkins slave setup. Now 
>> they are configured as 16vCPUs + 48GB of RAM per slave. Each time during a 
>> build, the CPU is always spiking at 100%. We are closing the build in 2h20m 
>> but the goal is to reach 1hr.
>>
>> What is the best way to do so? What type of tweaks in VMware? How can we 
>> push through the build faster?
>>
>> Thanks!
>> Alex
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to