Re: [Boost-testing] Too many results?

From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2007-09-27 20:54:55

K. Noel Belcourt wrote:
> On Sep 27, 2007, at 10:46 AM, Rene Rivera wrote:
> 
>> I've been watching my Linux machine take incrementally more and more
>> time processing the regression results and uploading them to the OSL
>> server. If I'm lucky not too many new results come in, and it takes  
>> 3.5
>> hours (it used to take about half that).
> 
> So I guess this might not be a good time to ask if I could ramp up  
> the number of build configurations I test every night?

Asking before doing it puts it automatically in the "good time" 
category. ;-)

> We would like to start testing
> 
> link=static,shared
> runtime-link=static,shared
> address-model=32,64
> threading=single,multi
> 
> I was hoping to start testing essentially this whole matrix on our  
> machines.  Will the testing system scale up if I were to start  
> testing this whole matrix?  Can anyone envision problems?

I can tell you that it will definitely *not* scale to handle that :-( I 
suspect my machine will be somewhat slow in processing so many results 
on an ongoing basis. So this leaves only a few options...

1. We figure out how to speed up the processing, an do it immediately. 
CPU, disk, and network are serious issues now since the reliability is 
essentially fixed just by not running the processing on a Windows machine.

2. We spread the processing load around many machines. For example we 
could have separate results for the variety of build variants.

3. We abandon the XSL processing now... But of course there's really no 
looming equivalent to replace it.

-- 
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo