<?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 Do inodes cache directory size? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/do-inodes-cache-directory-size/m-p/2778420#M76673</link>
    <description>If I run du on a directory, it's mch quicker the second time. Is this an artefact of memory caching or will it in fact remain faster? I'm asking because I have to do some heavy find'ing and I'll like to be able to prune on directory size checksums but there's no point if I use du to do this and it has to go through the whole tree anyway ...</description>
    <pubDate>Fri, 02 Aug 2002 11:25:13 GMT</pubDate>
    <dc:creator>Philip Kime</dc:creator>
    <dc:date>2002-08-02T11:25:13Z</dc:date>
    <item>
      <title>Do inodes cache directory size?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/do-inodes-cache-directory-size/m-p/2778420#M76673</link>
      <description>If I run du on a directory, it's mch quicker the second time. Is this an artefact of memory caching or will it in fact remain faster? I'm asking because I have to do some heavy find'ing and I'll like to be able to prune on directory size checksums but there's no point if I use du to do this and it has to go through the whole tree anyway ...</description>
      <pubDate>Fri, 02 Aug 2002 11:25:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/do-inodes-cache-directory-size/m-p/2778420#M76673</guid>
      <dc:creator>Philip Kime</dc:creator>
      <dc:date>2002-08-02T11:25:13Z</dc:date>
    </item>
    <item>
      <title>Re: Do inodes cache directory size?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/do-inodes-cache-directory-size/m-p/2778421#M76674</link>
      <description>It is memory caching.&lt;BR /&gt;&lt;BR /&gt;It will remain faster as long as the entries reside in cache.</description>
      <pubDate>Fri, 02 Aug 2002 12:05:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/do-inodes-cache-directory-size/m-p/2778421#M76674</guid>
      <dc:creator>John Bolene</dc:creator>
      <dc:date>2002-08-02T12:05:49Z</dc:date>
    </item>
    <item>
      <title>Re: Do inodes cache directory size?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/do-inodes-cache-directory-size/m-p/2778422#M76675</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;for the case you mentioned I would recommend to do only a single "find . -print" and redirect the ouput into a (temporary) file.&lt;BR /&gt;Then use "grep" on that file - much less trouble for your system, much faster for your results...&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Wodisch&lt;BR /&gt;</description>
      <pubDate>Sat, 03 Aug 2002 13:32:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/do-inodes-cache-directory-size/m-p/2778422#M76675</guid>
      <dc:creator>Wodisch_1</dc:creator>
      <dc:date>2002-08-03T13:32:10Z</dc:date>
    </item>
  </channel>
</rss>

