https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-1127 Lustre <p>To have proper repeatable performance testing on hyperion, our performance-sanity test needs to work. Performance-sanity can then be used for the performance section of release testing.</p> Hyperion LU-1127

need performance-sanity to work on Hyperion

Bug Minor Resolved Won't Fix Minh Diep Cliff White Tue, 21 Feb 2012 19:04:31 +0000 Mon, 15 Dec 2014 16:29:20 +0000 Mon, 15 Dec 2014 16:29:20 +0000 Lustre 2.2.0 Lustre 2.3.0 Lustre 2.1.1 0 4 <p>Is there a particular reason that we are using mdsrate in preference to mdtest? I understand that mdsrate was written originally for Lustre metadata testing, but I wonder if we could move over to mdtest and get equivalent functionality?</p> <p>My question/concern is about using the more standard mdtest benchmarking tool for Lustre performance testing, so that it is easier to compare results from mdtest to mdsrate.</p> <p>My comments aren't necessarily a request to change the tool being used right now, but more to start a discussion of whether we should move away from mdsrate in our scale testing.</p> <p>Majority of the time we had been using mdtest on hyperion. AFAIK, there are a few time that we needed to use mdsrate instead of mdtest were when mdtest hit a blocker while mdsrate did not. I noticed that DNE project were using mdsrate. Wang Di modified mdsrate to run with multiple mounts. Perhaps we should find out if we can do the same with mdtest. Adding Di to this.</p> <p>We've also had some issues keeping mdsrate running at Hyperion, I would not object to dropping it. As Minh said, we routinely run mdtest. </p> Development Rank 1|hzw05z: Rank (Obsolete) 10106 Severity