|
It would be useful for debugging performance problems if there was a list of client NIDs included in the "obdfilter.*.job_stats" output, so that it is possible to isolate which client(s) are causing a bad IO workload.
At the basic level it would just print a list of NIDs no particular order (though likely using an rbtree or hash for the NIDs would make it faster to check for new RPCs if the NID was already in the list rather than scanning a linked list).
It would be desirable to print the NIDs as ranges (e.g. 10.0.101.22-75,10.0.102.45-92 or similar) so that the output is not so verbose. This merging would only be needed when the job_stats file is read, so should not necessarily be done at stat collection time.
|