A system warmed up, may NOT be at 100% at all times.   It dependent on the relative workload presented to the system.<br><br>PAM can be 50% full..and be &#39;warmed up&#39;.<br><br><br>This starts to get into the subject of the math/history/etc of how long unreferenced blocks are kept in the pool.<br>
<br><br><br><div class="gmail_quote">On Mon, Sep 19, 2011 at 1:48 PM, Eugene Vilensky <span dir="ltr">&lt;<a href="mailto:evilensky@gmail.com">evilensky@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Mon, Sep 19, 2011 at 3:37 PM, Blake Golliher &lt;<a href="mailto:thelastman@gmail.com">thelastman@gmail.com</a>&gt; wrote:<br>
&gt; . (stats show -i<br>
&gt; 1 ext_cache_obj:ec0:usage for example).<br>
<br>
</div>Nitpicking on this example, isn&#39;t this a stat for % full?  That is, on<br>
a system which is warmed up, it should be at 100% at all times? I<br>
found this useful for what I needed to do with DFM and flash cache:<br>
<br>
<a href="http://communities.netapp.com/thread/8461" target="_blank">http://communities.netapp.com/thread/8461</a><br>
<div><div></div><div class="h5">_______________________________________________<br>
Toasters mailing list<br>
<a href="mailto:Toasters@teaparty.net">Toasters@teaparty.net</a><br>
<a href="http://www.teaparty.net/mailman/listinfo/toasters" target="_blank">http://www.teaparty.net/mailman/listinfo/toasters</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>---<br>Gustatus Similis Pullus<br>