[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [hobbit] New feature ?
- To: <hobbit (at) hswn.dk>
- Subject: RE: [hobbit] New feature ?
- From: "Stewart, Tom L." <Tom.Stewart (at) landsend.com>
- Date: Wed, 28 Nov 2007 08:35:38 -0600
- References: <BAC1D28A5AB852439A6914CA7AB4E63F05112460 (at) permls05.wde.woodside.com.au> <200711281039.14201.bgmilne (at) staff.telkomsa.net> <200711280511.11365.s_aiello (at) comcast.net>
- Thread-index: Acgxp1NClQq5qGekRziWBReizMzdkAAJIaWw
- Thread-topic: [hobbit] New feature ?
If you can have a standard host name convention, then you could use a
regex.
Tom
-----Original Message-----
From: s_aiello (at) comcast.net [mailto:s_aiello (at) comcast.net]
Sent: Wednesday, November 28, 2007 4:11 AM
To: hobbit (at) hswn.dk
Subject: Re: [hobbit] New feature ?
On Wednesday 28 November 2007, Buchan Milne wrote:
>
> But, IMHO, the threshold should be dependant more on the number of
> CPUs, rather than on the architecture. For example, we have a higher
> threshold on our X4600s (8 physical, dual core) than our X4100s/X4200s
> (2 physical, some dual-core).
>
> How many CPUs does the Sun T2000 have/report ?
>
I believe the T2000s report 32 processors, in reality there is only 1. 1
x 8 cores x 4 concurrent threads capable.
But for all our devices we normally set our LA thresholds by the
folowing
formula:
Warn: #CPU x 1
Panic: #CPU x 1.5
My hobbit-clients.cfg would be alot smaller if in the default section,
if I could use a formula definition for LOAD instead of a hardcoded
section.
>Instead of defining runqueue threshhold per host name, it would be nice
>to
have a ARCH option which could be overridden by the HOST
You could hardcode the client's CLASS option to it's arch, and be able
to do what you propose.
~Steve
To unsubscribe from the hobbit list, send an e-mail to
hobbit-unsubscribe (at) hswn.dk