<?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: filesystem performance in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/filesystem-performance/m-p/2619869#M645835</link>
    <description>For VxFS filesystems with primarily random access, use mincache=direct, convosync=direct&lt;BR /&gt;&lt;BR /&gt;For filesystems that you do not care about the data integrity in the event of a system failure, use tmplog or nolog, mincache=tmpcache, convosync=delay&lt;BR /&gt;&lt;BR /&gt;Be sure you have Online JFS and look at the man pages for fsadm_vxfs and mount_vxfs.</description>
    <pubDate>Mon, 26 Nov 2001 14:15:47 GMT</pubDate>
    <dc:creator>John Bolene</dc:creator>
    <dc:date>2001-11-26T14:15:47Z</dc:date>
    <item>
      <title>filesystem performance</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/filesystem-performance/m-p/2619867#M645833</link>
      <description>hello,&lt;BR /&gt;I have 1GB VxFS filesystem. It is used by an apllication, which creates many small (xx - 2xx kB) files. We can divide the files into two groups:&lt;BR /&gt;- read/write files,&lt;BR /&gt;- read/write files with locking,&lt;BR /&gt;We cannot switch off filesystem logging.&lt;BR /&gt;The question is: what mounting options should be used to minimize reading/writing time. &lt;BR /&gt;We cannot use kernel params for tunning because they've been already optimized.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance.</description>
      <pubDate>Mon, 26 Nov 2001 13:54:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/filesystem-performance/m-p/2619867#M645833</guid>
      <dc:creator>Marcin Wicinski</dc:creator>
      <dc:date>2001-11-26T13:54:49Z</dc:date>
    </item>
    <item>
      <title>Re: filesystem performance</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/filesystem-performance/m-p/2619868#M645834</link>
      <description>Hi Marcin:&lt;BR /&gt;&lt;BR /&gt;Everything is a trade between performance and integrity.  See Technical Knowledge Base document #KBRC00007737 for a good summary overview.  Remember that Online JFS is required.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Mon, 26 Nov 2001 14:00:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/filesystem-performance/m-p/2619868#M645834</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2001-11-26T14:00:56Z</dc:date>
    </item>
    <item>
      <title>Re: filesystem performance</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/filesystem-performance/m-p/2619869#M645835</link>
      <description>For VxFS filesystems with primarily random access, use mincache=direct, convosync=direct&lt;BR /&gt;&lt;BR /&gt;For filesystems that you do not care about the data integrity in the event of a system failure, use tmplog or nolog, mincache=tmpcache, convosync=delay&lt;BR /&gt;&lt;BR /&gt;Be sure you have Online JFS and look at the man pages for fsadm_vxfs and mount_vxfs.</description>
      <pubDate>Mon, 26 Nov 2001 14:15:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/filesystem-performance/m-p/2619869#M645835</guid>
      <dc:creator>John Bolene</dc:creator>
      <dc:date>2001-11-26T14:15:47Z</dc:date>
    </item>
  </channel>
</rss>

