For Solaris 10 x86, I use "iostat -xtcnr 1 2".
That'll do 2 iterations in 2 seconds. I throw away the first iteration
of iostat because it's historic data.
Then I capture the following columns from iostat:
my %gmetric_params = (
'r/s' => {
name => 'rps', # name override because / in r/s causes gmetad to
break
type => 'float',
units => 'read/s'
},
'w/s' => {
name => 'wps', # name override
type => 'float',
units => 'write/s'
},
'kr/s' => {
name => 'krps', # name override
type => 'float',
units => 'KB/s'
},
'kw/s' => {
name => 'kwps', # name override
type => 'float',
units => 'KB/s'
},
asvc_t => {
type => 'float',
units => "ms"
}
);
For Linux, I modified the script to use "iostat -x" and to parse to
capture similar fields.
-Paul
Bernard Li wrote:
> Hi guys:
>
> I am curious as to what folks usually do to measure block device I/O
> bandwidth (MB/s) with their Ganglia installation. Talking
> specifically about disk I/O, do you guys usually just use the output
> of iostat -k or something like that?
>
> Thanks,
>
> Bernard
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Ganglia-general mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/ganglia-general
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Ganglia-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ganglia-general
