[jboss-dev] RE: Differrences in CC runs for the AS testsuite

[Aleksandar Kostadinov]

Actually seems like the physical machine produced slow runs that is not
good.

Rajesh Rajasekaran wrote, On 06/19/2007 11:06 PM (EEST):
> I am not aware if this is a vmware server or ESX or GSX.
> The host OS is RHEL4, the box is x86_64, 2 cpu (Xeon 3Ghz).
> The vmware image is also RHEL4 with 1GB memory allocated.
> 
> I think there are around 20 instances running on this vmware server. IT
> might have a better idea about that and about tracking disk usage.
> 
> 
> -----Original Message-----
> From: jboss-qa-bounces at redhat.com [mailto:jboss-qa-bounces at redhat.com] On
> Behalf Of Carlo de Wolf
> Sent: Tuesday, June 19, 2007 2:44 PM
> To: JBoss.org development list
> Cc: 'Dimitris Andreadis'; QA
> Subject: Re: [jboss-dev] RE: Differrences in CC runs for the AS testsuite
> 
> Ah, that might explain a lot. Is it ESX, GSX or server?
> What is the host os?
> How many instances are up and running?
> Do you keep track of disk i/o used by each instance?
> 
> I regularly see vmware 'hanging' for a couple of seconds up to half a
> minute to sync up it's image on disk. That's WS on Vista and XP.
> 
> Carlo
> 
> On Tue, 2007-06-19 at 14:19 -0500, Rajesh Rajasekaran wrote:
>> This is a vmware instance used only for projects that require frequent
> runs,
>> only jboss-4.2-testsuite at this time, doesn't have parallel runs going
> on.
>>
>> -----Original Message-----
>> From: Dimitris Andreadis [mailto:dandread at redhat.com] 
>> Sent: Tuesday, June 19, 2007 2:15 PM
>> To: Rajesh Rajasekaran
>> Cc: 'JBoss.org development list'; QA
>> Subject: Re: Differrences in CC runs for the AS testsuite
>>
>> That would explain the major time difference. What about the other
> machine?
>> Is it doing a 
>> 'single' CC run at a time or multiple ones (like different projects) ?
>>
>> Rajesh Rajasekaran wrote:
>>> This testsuite runs currently on 2 different machines. 
>>> Looking at the runs over the last 10 days,
>>> The runs which are scheduled to run frequently takes anywhere from 150 -
>> 180
>>> minutes.
>>> The nightly run which goes on a different machine takes 220+ minutes.
>>> (I am disabling this nightly run to avoid confusion).
>>>
>>> At least now we have a lesser margin to worry about (150-180 min). 
>>>
>>>
>>> -----Original Message-----
>>> From: jboss-qa-bounces at redhat.com [mailto:jboss-qa-bounces at redhat.com]
> On
>>> Behalf Of Dimitris Andreadis
>>> Sent: Tuesday, June 19, 2007 1:49 PM
>>> To: JBoss.org development list; QA
>>> Subject: Differrences in CC runs for the AS testsuite
>>>
>>> The exact same CC run for jboss-4.2-testsuite-sun-1.5 with close to zero
>>> code changes, took 
>>> at different times:
>>>
>>>
> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.2-testsuite-sun-1.5?l
>>> og=log20070619084727Lbuild.42
>>> 171 minutes 32 seconds
>>>
>>>
> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.2-testsuite-sun-1.5?l
>>> og=log20070619114948
>>> 159 minutes 47 seconds
>>>
>>>
> http://cruisecontrol.jboss.com/cc/buildresults/jboss-4.2-testsuite-sun-1.5?l
>>> og=log20070619102946
>>> 227 minutes 51 seconds
>>>
>>> So the slowest run took 42% more time than the fastest run. Obviously
> this
>>> has an impact in 
>>> all time sensitive tests.
>>>
>>> Is the CC machine loaded with other stuff? What else could explain the
>> time
>>> differences?
>>>
>>>
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
> 
>