WARNING: This is the _old_ Lustre wiki, and it is in the process of being retired. The information found here is all likely to be out of date. Please search the new wiki for more up to date information.
Metadata Performance Project: Difference between revisions
From Obsolete Lustre Wiki
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
The project leader is [mailto:Nirant.Puntambekar@sun.com Nirant Puntambekar]. | The project leader is [mailto:Nirant.Puntambekar@sun.com Nirant Puntambekar]. | ||
You can track the progress of this project | You can track the progress of this project through the [http://wiki.lustre.org/index.php/File:MetaData_Performance_Project_Dashboard.pdf project dashboard] that Nirant updates bi-weekly. | ||
Also, baseline metadata performance tests being done by the Lustre team are soon to be published on this page. | Also, baseline metadata performance tests being done by the Lustre team are soon to be published on this page. | ||
Revision as of 12:57, 12 May 2009
MetaData Performance Project
This is a joint project that the Lustre team, the ORNL LCE, and Cray created in early spring of 2009. The project has the following primary goals:
- Understand current Lustre 1.6, 1.8, and 2.0 branch metadata performance characteristics
- Ensure the Lustre 1.6 branch performs as well as previous Lustre branches with respect to metadata
- Double the current average performance of Lustre 1.8 branch metadata performance
- Though introduction of clustered metadata early exposure in Lustre 2.0 and until the general release of CMD, ensure that Lustre metadata scales and performs as well as, or better than, GPFS metadata scaling
The project leader is Nirant Puntambekar.
You can track the progress of this project through the project dashboard that Nirant updates bi-weekly.
Also, baseline metadata performance tests being done by the Lustre team are soon to be published on this page.
