BWG File System Monitoring: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 27: | Line 27: | ||
Status-ey Stuff | Status-ey Stuff | ||
* [http://wiki.opensfs.org/images/e/ec/LUG_2013_OpenSFS_BWG_update.pdf LUG 2013 Report] (final ppt). | * [http://wiki.opensfs.org/images/e/ec/LUG_2013_OpenSFS_BWG_update.pdf LUG 2013 Report] (final ppt). | ||
Return to [[Benchmarking_Working_Group|Benchmarking Working Group]] page. | Return to [[Benchmarking_Working_Group|Benchmarking Working Group]] page. |
Revision as of 12:52, 16 December 2014
The task of the BWG File System Monitoring group is to:
- develop a list of existing parallel filesystem monitoring tools.
- identify their capabilities, add any others we think should exist.
- compare and contrast the tools to each other and the capabilities we think should exist.
Scenario:
You've just deployed a copy of Spider II at your site. Now you need to instrument it a) to detect if a component has failed, b) to ensure you are meeting your target performance numbers, and c) to determine what future improvements can be made.
- Where do you start?
- What information do you think you should collect?
- What tools/utilities/commands do you reach for?
The Features List - what to monitor.
The Tools List - how to monitor.
An IO Process Model to get an idea of the space of variables that are usefully monitored.
Status-ey Stuff
- LUG 2013 Report (final ppt).
Return to Benchmarking Working Group page.