<font size=2 face="sans-serif">FILE_HEAT value is a non-negative floating
point value. The value can grow quite large -- in theory it can grow
to the IEEE 64 bit maximum floating point value and maybe even to "infinity".
</font><br><br><font size=2 face="sans-serif">Each time a file is read completely
from disk it's FILE_HEAT value increases by 1. If a fraction, f,
of the file is read then FILE_HEAT += f. (f<=1)</font><br><font size=2 face="sans-serif">On the other hand, as time passes the
FILE_HEAT "decays" at the rate given by the (mmchconfig) parameters
fileHeatPeriodMinutes and fileHeatLossPercent.</font><br><br><font size=2 face="sans-serif">In fact I recently corresponding with
a customer (who is no stranger to this forum and may wish to comment!)
who found that a bunch of hot little script files had accumulated heat
values greater than 100,000,000 ! We were both surprised.
Apparently these files are read and re-read many times every day by many
nodes and so their heat builds up! </font><br><font size=2 face="sans-serif"><br>So what would you call "Hot", "Warm", "Cold"?
It depends... To get a good idea, I suggest that a "survey"
of FILE_HEAT values be done by using an mmapplypolicy command with a rule
like.</font><br><br><font size=2 face="sans-serif">rule 'y' list 'fhn0' weight(FILE_HEAT)</font><br><font size=2 face="sans-serif"> SHOW(HEX(XATTR('gpfs.FileHeat'))
||</font><br><font size=2 face="sans-serif"> ' A=' || varchar(ACCESS_TIME)
||</font><br><font size=2 face="sans-serif"> ' K=' || varchar(KB_ALLOCATED)
||</font><br><font size=2 face="sans-serif"> ' H=' || varchar(FILE_HEAT))</font><br><br><font size=2 face="sans-serif"> where FILE_HEAT != 0.0</font><br><br><font size=2 face="sans-serif">Using `mmapplypolicy FS -P policy-rules-file
-I defer -f /tmp/whatever [other options such as... -N nodeclass
-g /shared-temp ... ]</font><br><br><font size=2 face="sans-serif">This will produce a file list sorted
by FILE_HEAT, which you can then peruse or otherwise process....</font><br><font size=2 face="sans-serif">Perhaps a histogram or other display
of (number of files) vs (heat values) would be interesting...</font><br><br><br><br><br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Andreas Landhuer
<alandhae@gmx.de></font><br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">gpfsug-discuss@spectrumscale.org</font><br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">10/04/2016 08:54 AM</font><br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">[gpfsug-discuss]
Fileheat reporting</font><br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">gpfsug-discuss-bounces@spectrumscale.org</font><br><hr noshade><br><br><br><tt><font size=2><br>Customer needs a report of filenames being Hot, warm and cold.<br><br>As far as I'm understanding fileheat can be any value larger than zero.<br>A value of zero or almost zero equals to COLD<br><br>How am I classifying warm and hot?<br><br>I'm needing a standardized value between 0 and 1 for fileheat. Is it <br>possible creating such a number when when activating fileheat and creating
<br>reports and finally using ILM policies according to this classification?<br><br>Best regards<br><br>Andreas<br><br><br><br>-- <br>Andreas Landhuer
+49 151 12133027 (mobile)<br>alandhae@gmx.de_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at spectrumscale.org<br></font></tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss"><tt><font size=2>http://gpfsug.org/mailman/listinfo/gpfsug-discuss</font></tt></a><tt><font size=2><br></font></tt><br><BR>