<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
Hi All,
<div class=""><br class="">
</div>
<div class="">In the README for the mmfind command it says:</div>
<div class="">
<div class=""><br class="">
</div>
<div class="">mmfind</div>
<div class=""> A highly efficient file system traversal tool, designed to serve</div>
<div class=""> as a drop-in replacement for the 'find' command as used against GPFS FSes.</div>
</div>
<div class=""><br class="">
</div>
<div class="">And:</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">mmfind is expected to be slower than find on file systems with relatively few inodes.</div>
<div class="">This is due to the overhead of using mmapplypolicy.</div>
<div class="">However, if you make use of the -exec flag to carry out a relatively expensive operation </div>
<div class="">on each file (e.g. compute a checksum), using mmfind should yield a significant performance </div>
<div class="">improvement, even on a file system with relatively few inodes.</div>
</div>
<div class=""><br class="">
</div>
<div class="">I have a list of just shy of 50 inode numbers that I need to figure out what file they correspond to, so I decided to give mmfind a try:</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">+ cd /usr/lpp/mmfs/samples/ilm</div>
<div class="">+ ./mmfind /gpfs23 -inum 113769917 -o -inum 132539418 -o -inum 135584191 -o -inum 136471839 -o -inum 137009371 -o -inum 137314798 -o -inum 137939675 -o -inum 137997971 -o -inum 138013736 -o -inum 138029061 -o -inum 138029065 -o -inum 138029076
-o -inum 138029086 -o -inum 138029093 -o -inum 138029099 -o -inum 138029101 -o -inum 138029102 -o -inum 138029106 -o -inum 138029112 -o -inum 138029113 -o -inum 138029114 -o -inum 138029119 -o -inum 138029120 -o -inum 138029121 -o -inum 138029130 -o -inum
138029131 -o -inum 138029132 -o -inum 138029141 -o -inum 138029146 -o -inum 138029147 -o -inum 138029152 -o -inum 138029153 -o -inum 138029154 -o -inum 138029163 -o -inum 138029164 -o -inum 138029165 -o -inum 138029174 -o -inum 138029175 -o -inum 138029176
-o -inum 138083075 -o -inum 138083148 -o -inum 138083149 -o -inum 138083155 -o -inum 138216465 -o -inum 138216483 -o -inum 138216507 -o -inum 138216535 -o -inum 138235320 -ls</div>
</div>
<div class=""><br class="">
</div>
<div class="">I kicked that off last Friday and it is _still_ running. By comparison, I have a Perl script that I have run in the past that simple traverses the entire filesystem tree and stat’s each file and outputs that to a log file. That script would
“only” run ~24 hours.</div>
<div class=""><br class="">
</div>
<div class="">Clearly mmfind as I invoked it is much slower than the corresponding Perl script, so what am I doing wrong? Thanks…</div>
<div class=""><br class="">
</div>
<div class="">Kevin</div>
<br class="">
<div class="">
<div class="">—</div>
<div class="">Kevin Buterbaugh - Senior System Administrator</div>
<div class="">Vanderbilt University - Advanced Computing Center for Research and Education</div>
<div class=""><a href="mailto:Kevin.Buterbaugh@vanderbilt.edu" class="">Kevin.Buterbaugh@vanderbilt.edu</a> - (615)875-9633</div>
<div class=""><br class="">
</div>
<br class="Apple-interchange-newline">
</div>
<br class="">
</body>
</html>