<?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: Memory Fragmentation in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/memory-fragmentation/m-p/2495092#M805550</link>
    <description>I don't believe there is any benefit to having concurrent virtual pages mapped to concurrent physical pages.  The hardware still has to go through the Translation Lookaside Buffer to convert a virtual address to physical.&lt;BR /&gt;&lt;BR /&gt;Depending on the application's memory access patters, you may get a significant performance boost on HP-UX 11.0 by increasing the page size.  If the appliation does sparse memory accesses, then increasing the page size will reduce the number of TLB lookups (and thus the possibility of expensive TLB misses).&lt;BR /&gt;&lt;BR /&gt;To increase the page size of an application, use chatr like...&lt;BR /&gt;&lt;BR /&gt;   chatr +pd 64K a.out&lt;BR /&gt;&lt;BR /&gt;See the chatr manpage for more info.&lt;BR /&gt;&lt;BR /&gt;-sam</description>
    <pubDate>Fri, 16 Feb 2001 20:16:28 GMT</pubDate>
    <dc:creator>Sam Nicholls</dc:creator>
    <dc:date>2001-02-16T20:16:28Z</dc:date>
    <item>
      <title>Memory Fragmentation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/memory-fragmentation/m-p/2495091#M805549</link>
      <description>Can main memory fragmentation cause significant performance problems?</description>
      <pubDate>Fri, 16 Feb 2001 19:20:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/memory-fragmentation/m-p/2495091#M805549</guid>
      <dc:creator>ASOEASTGEOGRAPHY</dc:creator>
      <dc:date>2001-02-16T19:20:56Z</dc:date>
    </item>
    <item>
      <title>Re: Memory Fragmentation</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/memory-fragmentation/m-p/2495092#M805550</link>
      <description>I don't believe there is any benefit to having concurrent virtual pages mapped to concurrent physical pages.  The hardware still has to go through the Translation Lookaside Buffer to convert a virtual address to physical.&lt;BR /&gt;&lt;BR /&gt;Depending on the application's memory access patters, you may get a significant performance boost on HP-UX 11.0 by increasing the page size.  If the appliation does sparse memory accesses, then increasing the page size will reduce the number of TLB lookups (and thus the possibility of expensive TLB misses).&lt;BR /&gt;&lt;BR /&gt;To increase the page size of an application, use chatr like...&lt;BR /&gt;&lt;BR /&gt;   chatr +pd 64K a.out&lt;BR /&gt;&lt;BR /&gt;See the chatr manpage for more info.&lt;BR /&gt;&lt;BR /&gt;-sam</description>
      <pubDate>Fri, 16 Feb 2001 20:16:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/memory-fragmentation/m-p/2495092#M805550</guid>
      <dc:creator>Sam Nicholls</dc:creator>
      <dc:date>2001-02-16T20:16:28Z</dc:date>
    </item>
  </channel>
</rss>

