[Lustre-discuss] lustre dstat plugin

[Brock Palen]

On Mar 9, 2008, at 10:03 PM, Aaron Knister wrote:

> Just wondering if either of you have used collectl if/and which you  
> prefer- dstat or collectl.

Never used it, Looks like they solve the same problem.  I like dstat  
for the simple plugins. (if your a better python programer than me).   
And how you can pull our results, like I use the following on our  
lustre OSS with two OST's sda and sdb.

dstat -D sda,sdb,total

That gives me per disk stats and a total.

Similar tools could be made for collectl I'm sure.

Brock

>
> -Aaron
>
> On Mar 7, 2008, at 7:03 PM, Brock Palen wrote:
>
>> On Mar 7, 2008, at 6:58 PM, Kilian CAVALOTTI wrote:
>>
>>> Hi Brock,
>>>
>>> On Wednesday 05 March 2008 05:21:51 pm Brock Palen wrote:
>>>> I have wrote a lustre dstat plugin.  You can find it on my blog:
>>>
>>> That's cool! Very useful for my daily work, thanks!
>>
>> Thanks!  Its the first python I ever wrote.
>>
>>>
>>>> It only works on clients, and has not been tested on multiple  
>>>> mounts,
>>>> Its very simple just reads /proc/
>>>
>>> It indeed doesn't read stats for multiple mounts. I slightly
>>> modified it
>>> so it can display read/write numbers for all the mounts it founds  
>>> (see
>>> the attached patch).
>>
>> This is great idea
>>
>>>
>>> Here's a typical output for a rsync transfer from scrath to home:
>>>
>>> -- 8<  
>>> ---------------------------------------------------------------
>>> $ dstat -M lustre
>>>
>>> Module dstat_lustre is still experimental.
>>> --scratch-------home---
>>> read write: read write
>>> 110M    0 :   0   110M
>>> 183M    0 :   0   183M
>>> 184M    0 :   0   184M
>>> -- 8<  
>>> ---------------------------------------------------------------
>>>
>>> Maybe it could be useful to also add the other metrics from the stat
>>> file, but I'm not sure which ones would be the more relevant. And it
>>> would probably be wise to do that in a separate module, like
>>> lustre_stats, to avoid clutter.
>>
>> Yes,  dstat comes with plugins for nfsv3  and has two modules,
>>
>> dstat_nfs3  and dstat_nfs3op  which has extended details.  So I think
>> this would be a good idea to follow that model.
>>
>>>
>>> Anyway, great job, and thanks for sharing it!
>>
>> Thanks again.
>>
>>> Cheers,
>>> -- 
>>> Kilian<dstat_lustre.diff>
>>
>> _______________________________________________
>> Lustre-discuss mailing list
>> Lustre-discuss at lists.lustre.org
>> http://lists.lustre.org/mailman/listinfo/lustre-discuss
>
> Aaron Knister
> Associate Systems Analyst
> Center for Ocean-Land-Atmosphere Studies
>
> (301) 595-7000
> aaron at iges.org
>
>
>
>
>
>