<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Flash Pool - AWA detailed output - Low cacheable reads with high read hit rate in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Flash-Pool-AWA-detailed-output-Low-cacheable-reads-with-high-read-hit-rate/m-p/155271#M34921</link>
    <description>&lt;P&gt;Hello Paul,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I just wanted to understand that output. There are other volumes with apparently strange values. Take a look:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Volume #3 vol_ZXC&lt;BR /&gt;Summary of the past 7 intervals&lt;BR /&gt;max&lt;BR /&gt;------------&lt;BR /&gt;Read Throughput (MB/s): 17.398&lt;BR /&gt;Write Throughput (MB/s): 3.266&lt;BR /&gt;Cacheable Read (%): 0&lt;BR /&gt;Cacheable Write (%): 0&lt;BR /&gt;Max Projected Cache Size (GiB): 0.036&lt;BR /&gt;Projected Read Hit (%): 12&lt;BR /&gt;Projected Write Hit (%): 0&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;"No cacheable data" but 12% read hit, top 3. How come?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Besides that it would be nice to understand what are the metrics that made up this top 8 rank. Looking at them does not seem to translate the aggregate recommendation.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Pedro&lt;/P&gt;</description>
    <pubDate>Thu, 02 Apr 2020 18:51:04 GMT</pubDate>
    <dc:creator>pedro_rocha</dc:creator>
    <dc:date>2020-04-02T18:51:04Z</dc:date>
    <item>
      <title>Flash Pool - AWA detailed output - Low cacheable reads with high read hit rate</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Flash-Pool-AWA-detailed-output-Low-cacheable-reads-with-high-read-hit-rate/m-p/155245#M34916</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I am trying to analyze Flash Pool candidacy and optimal cache size for an ONTAP cluster. It is running ONTAP 9.3P13. I followed the instructions on this &lt;A href="https://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.dot-cm-psmg%2FGUID-2C3EC0DF-FEFE-4871-A161-4A3BAC87DB69.html&amp;amp;resultof=%22%61%77%61%22%20" target="_self"&gt;link&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So far so good, been able to interpret most of its output. But then I tried to see the detailed output using the -t option in the print command. It&amp;nbsp;shows information about the volumes in the aggregate that are the &lt;U&gt;&lt;STRONG&gt;best candidates for being on a Flash Pool aggregate&lt;/STRONG&gt;&lt;/U&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Happens that for a specific aggregate, the #1 volume in the list is the following:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;Volume #1 VOL_XYZ&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Summary of the past 7 intervals&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;max&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;------------&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Read Throughput (MB/s): 21.545&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Write Throughput (MB/s): 12.757&lt;/EM&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;EM&gt;Cacheable Read (%): 0&lt;/EM&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;EM&gt;Cacheable Write (%): 12&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Max Projected Cache Size (GiB): 1.856&lt;/EM&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;EM&gt;Projected Read Hit (%): 50&lt;/EM&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;EM&gt;Projected Write Hit (%): 8&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So, could someone explain why and how could this volume have 0% of cacheable reads and even so present a Projected Read Hit of 50%?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Pedro Rocha.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 11:14:34 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Flash-Pool-AWA-detailed-output-Low-cacheable-reads-with-high-read-hit-rate/m-p/155245#M34916</guid>
      <dc:creator>pedro_rocha</dc:creator>
      <dc:date>2025-06-04T11:14:34Z</dc:date>
    </item>
    <item>
      <title>Re: Flash Pool - AWA detailed output - Low cacheable reads with high read hit rate</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Flash-Pool-AWA-detailed-output-Low-cacheable-reads-with-high-read-hit-rate/m-p/155267#M34920</link>
      <description>&lt;P&gt;Because it is inserted with the writes. If you need specific help,&amp;nbsp; your SE on your account team can help you review the AWA output as well.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Apr 2020 14:33:22 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Flash-Pool-AWA-detailed-output-Low-cacheable-reads-with-high-read-hit-rate/m-p/155267#M34920</guid>
      <dc:creator>paul_stejskal</dc:creator>
      <dc:date>2020-04-02T14:33:22Z</dc:date>
    </item>
    <item>
      <title>Re: Flash Pool - AWA detailed output - Low cacheable reads with high read hit rate</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Flash-Pool-AWA-detailed-output-Low-cacheable-reads-with-high-read-hit-rate/m-p/155271#M34921</link>
      <description>&lt;P&gt;Hello Paul,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I just wanted to understand that output. There are other volumes with apparently strange values. Take a look:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Volume #3 vol_ZXC&lt;BR /&gt;Summary of the past 7 intervals&lt;BR /&gt;max&lt;BR /&gt;------------&lt;BR /&gt;Read Throughput (MB/s): 17.398&lt;BR /&gt;Write Throughput (MB/s): 3.266&lt;BR /&gt;Cacheable Read (%): 0&lt;BR /&gt;Cacheable Write (%): 0&lt;BR /&gt;Max Projected Cache Size (GiB): 0.036&lt;BR /&gt;Projected Read Hit (%): 12&lt;BR /&gt;Projected Write Hit (%): 0&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;"No cacheable data" but 12% read hit, top 3. How come?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Besides that it would be nice to understand what are the metrics that made up this top 8 rank. Looking at them does not seem to translate the aggregate recommendation.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Pedro&lt;/P&gt;</description>
      <pubDate>Thu, 02 Apr 2020 18:51:04 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Flash-Pool-AWA-detailed-output-Low-cacheable-reads-with-high-read-hit-rate/m-p/155271#M34921</guid>
      <dc:creator>pedro_rocha</dc:creator>
      <dc:date>2020-04-02T18:51:04Z</dc:date>
    </item>
  </channel>
</rss>

