server burn-in process recommendations?

Paul jpb at entel.ca
Tue Sep 22 21:58:14 UTC 2009


Furnish, Trever G wrote:
>> -----Original Message-----
>> From: redhat-list-bounces at redhat.com [mailto:redhat-list-
>> bounces at redhat.com] On Behalf Of Barry Brimer
>> Sent: Monday, September 21, 2009 1:04 PM
>> To: General Red Hat Linux discussion list
>> Subject: Re: server burn-in process recommendations?
>>
>>     
>>> Anyone have any recommendations on how best to burn in and test new
>>>       
>> RHEL
>>     
>>> systems?
>>>       
>> Have you looked at Inquisitor?  <http://www.inquisitor.ru/about/>
>>
>> Barry
>>     
>
> Thanks, Barry.  Hadn't heard of Inquisitor.  Have you used this product
> and been happy with it?
>
> I was actually thinking not of testing on bare hardware, but rather of
> suggestions on how to test performance following the install of the OS.
>
> For example, imagine we do an install of RHEL5 and everything appears to
> go well.  During boot we see a few messages fly by about various things
> being disabled, but we can't read them.  The system appears to operate
> normal when eyeballing it, but we don't notice that access to the system
> disks is going only 1/4 its normal speed.  I'd like us to notice before
> we release the machine to internal customers.
>
> I would think one of the OS-level benchmark suites would fit the bill,
> but I was hoping someone on the list would already have gone through
> that process of choosing the tests to run and could offer some advise
> from experience.
>
> --
> Trever
>   
I've never bothered to do any tests like this, as I've never had a
reason to. This is Linux after all, not Windows :)

You could try this: http://lbs.sourceforge.net/

Checking logs is a good way to examine all those messages that fly past
when you boot.

/var/log/boot.log
/var/log/messages

Cheers,


-- 


Paul





More information about the redhat-list mailing list