From Fedora Project Wiki
< Features
(Feature NFSometer has been accepted for F18 by FESCo on the Jul 30 meeting (ticket #925)) |
|||
| (19 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
= | = NFSometer <!-- The name of your feature --> = | ||
== Summary == | == Summary == | ||
<!-- A sentence or two summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release. --> | <!-- A sentence or two summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release. --> | ||
| Line 24: | Line 24: | ||
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | <!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | ||
NFSometer is designed to automate the running of existing filesystem benchmarks, gather NFS specific statistics and generate reports that make benchmark output more understandable. | NFSometer is designed to automate the running of existing filesystem benchmarks, gather NFS specific statistics and generate reports that make benchmark output more understandable. | ||
Goals: | |||
- Automate the time consuming process of running a variety of workloads looking for performance regressions between kernel versions, NFS protocol versions and NFS options. | |||
- Generate reports that allows the user to understand the performance characteristics of workloads and easily compare performance characteristics of different configurations. | |||
- Provide a simple way to define workloads. This allows users to evaluate NFS deployment scenarios with workloads representative of their unique needs. | |||
== Benefit to Fedora == | == Benefit to Fedora == | ||
<!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?--> | <!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?--> | ||
The inclusion of nfsometer benefits Fedora by providing customers with a tool to test NFS deployment scenarios before deployment. It is our hope this will increase adoption of NFSv4 and pNFS. | |||
== Scope == | == Scope == | ||
<!-- What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
At this point, all of the development is done. The scope of change that will effect the over all distribution is very small. NFSometer is a standalone package use to test NFS with other test sites and graph the results. | |||
== How To Test == | == How To Test == | ||
| Line 45: | Line 52: | ||
3. What are the expected results of those actions? | 3. What are the expected results of those actions? | ||
--> | --> | ||
There is no special hardware or data needed to test NFSometer. | |||
The following packages are needed to run NFSometer: | |||
nfs-utils python-matplotlib numpy python-mako filebench | |||
Examples assume there is an NFS server 'server.example.com' exporting a filesystem ('/export'). | |||
NOTE: the default arguments for nfsometer test NFSv4.1, but that is disabled on Fedora NFS servers right now. These examples assume v4.1 is enabled on the server. | |||
== User Experience == | == User Experience == | ||
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | <!-- If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | ||
Users may use NFSometer to check the stability and performances of their NFS environment. | |||
== Dependencies == | == Dependencies == | ||
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel feature)? --> | <!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel feature)? --> | ||
* numpy, python-matplotlib, python-mako, nfs-utils | |||
== Contingency Plan == | == Contingency Plan == | ||
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | <!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | ||
* None necessary for a contingency plan. All the development is done. | |||
== Documentation == | == Documentation == | ||
<!-- Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | <!-- Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | ||
* | * website: http://wiki.linux-nfs.org/wiki/index.php/NFSometer | ||
* GIT tree: http://git.linux-nfs.org/?p=dros/nfsometer.git;a=blob;f=README | |||
== Release Notes == | == Release Notes == | ||
<!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ --> | <!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ --> | ||
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. --> | <!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. --> | ||
* | * NFSometer is a performance measurement framework for running workloads and reporting results across NFS protocol versions, NFS options and Linux NFS client implementations. More detailed information can be found at: | ||
http://wiki.linux-nfs.org/wiki/index.php/NFSometer | |||
== Comments and Discussion == | == Comments and Discussion == | ||
* See [[Talk:Features/ | * See [[Talk:Features/NFSometer]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page --> | ||
[[Category: | [[Category:FeatureAcceptedF18]] | ||
<!-- When your feature page is completed and ready for review --> | <!-- When your feature page is completed and ready for review --> | ||
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler --> | <!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler --> | ||
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--> | <!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete--> | ||
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process --> | <!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process --> | ||
Latest revision as of 12:55, 31 July 2012
NFSometer
Summary
NFSometer is a performance measurement framework for running workloads and reporting results across NFS protocol versions, NFS options and Linux NFS client implementations.
Owner
- Name: Steve Dickson
- Email: steved@fedoraproject.org
Current status
- Targeted release: Fedora 18
- Last updated: Tue Jul 24, 2012
- Percentage of completion: 100%
Detailed Description
NFSometer is designed to automate the running of existing filesystem benchmarks, gather NFS specific statistics and generate reports that make benchmark output more understandable.
Goals:
- Automate the time consuming process of running a variety of workloads looking for performance regressions between kernel versions, NFS protocol versions and NFS options. - Generate reports that allows the user to understand the performance characteristics of workloads and easily compare performance characteristics of different configurations. - Provide a simple way to define workloads. This allows users to evaluate NFS deployment scenarios with workloads representative of their unique needs.
Benefit to Fedora
The inclusion of nfsometer benefits Fedora by providing customers with a tool to test NFS deployment scenarios before deployment. It is our hope this will increase adoption of NFSv4 and pNFS.
Scope
At this point, all of the development is done. The scope of change that will effect the over all distribution is very small. NFSometer is a standalone package use to test NFS with other test sites and graph the results.
How To Test
There is no special hardware or data needed to test NFSometer. The following packages are needed to run NFSometer:
nfs-utils python-matplotlib numpy python-mako filebench
Examples assume there is an NFS server 'server.example.com' exporting a filesystem ('/export'). NOTE: the default arguments for nfsometer test NFSv4.1, but that is disabled on Fedora NFS servers right now. These examples assume v4.1 is enabled on the server.
User Experience
Users may use NFSometer to check the stability and performances of their NFS environment.
Dependencies
- numpy, python-matplotlib, python-mako, nfs-utils
Contingency Plan
- None necessary for a contingency plan. All the development is done.
Documentation
- website: http://wiki.linux-nfs.org/wiki/index.php/NFSometer
- GIT tree: http://git.linux-nfs.org/?p=dros/nfsometer.git;a=blob;f=README
Release Notes
- NFSometer is a performance measurement framework for running workloads and reporting results across NFS protocol versions, NFS options and Linux NFS client implementations. More detailed information can be found at:
http://wiki.linux-nfs.org/wiki/index.php/NFSometer