<?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: SYSMEM increasing in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/sysmem-increasing/m-p/4934302#M803889</link>
    <description>Just noticed that I posted under wrong category. This thread will be closed and I will post it again under system administration.</description>
    <pubDate>Tue, 18 Oct 2005 09:00:20 GMT</pubDate>
    <dc:creator>Glen Liu</dc:creator>
    <dc:date>2005-10-18T09:00:20Z</dc:date>
    <item>
      <title>SYSMEM increasing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sysmem-increasing/m-p/4934300#M803887</link>
      <description>Sysadms,&lt;BR /&gt;&lt;BR /&gt;I have 2 11.11 systems running MC/SG and Sybase. The memory configuration is tight that the memory usage on the prod node is always flipping between 99% and 100%. 6.7G out of 8G mem is used by Sybase.&lt;BR /&gt;&lt;BR /&gt;Yesterday we had a fail-over testing. But the package couldnot be started on the stand-by node as Sybase couldnot get enough shared memory. There was 1.27G SYSMEM in glance while the same factor on the prod was only 608MB. The last reboot was back to 4 months ago on both servers. After reboot, the SYSMEM dropped to 700MB level on the stand-by node and Sybase started up.&lt;BR /&gt;&lt;BR /&gt;I am wondering what caused the SYSMEM increased on the Stand-by node. I check the articles in ftp://eh:spear9@hprc.external.hp.com/memory.htm It's very useful. I am suspecting maybe it's because of the Superpage pool. &lt;BR /&gt;&lt;BR /&gt;So my question is: What's Superpage pool? And what does it do? &lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;BR /&gt;&lt;BR /&gt;Glen</description>
      <pubDate>Mon, 17 Oct 2005 16:52:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sysmem-increasing/m-p/4934300#M803887</guid>
      <dc:creator>Glen Liu</dc:creator>
      <dc:date>2005-10-17T16:52:25Z</dc:date>
    </item>
    <item>
      <title>Re: SYSMEM increasing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sysmem-increasing/m-p/4934301#M803888</link>
      <description>More detail:&lt;BR /&gt;&lt;BR /&gt;The both nodes are identical on every thing. The stand-by node runs nothing if the package was not on it. This is the first fail-over testing, or say the first time pakcage running on the stand-by node, sice the last reboot 4 months ago.</description>
      <pubDate>Mon, 17 Oct 2005 17:08:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sysmem-increasing/m-p/4934301#M803888</guid>
      <dc:creator>Glen Liu</dc:creator>
      <dc:date>2005-10-17T17:08:04Z</dc:date>
    </item>
    <item>
      <title>Re: SYSMEM increasing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sysmem-increasing/m-p/4934302#M803889</link>
      <description>Just noticed that I posted under wrong category. This thread will be closed and I will post it again under system administration.</description>
      <pubDate>Tue, 18 Oct 2005 09:00:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sysmem-increasing/m-p/4934302#M803889</guid>
      <dc:creator>Glen Liu</dc:creator>
      <dc:date>2005-10-18T09:00:20Z</dc:date>
    </item>
  </channel>
</rss>

