<?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: on increasing data segment size in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/on-increasing-data-segment-size/m-p/2763662#M894401</link>
    <description>Jut to add to Bill's answer. You should not experience any change in performance when doing these changes. But as always with tuning only doing it will tell for sure.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Trond</description>
    <pubDate>Wed, 17 Jul 2002 05:42:10 GMT</pubDate>
    <dc:creator>Trond Haugen</dc:creator>
    <dc:date>2002-07-17T05:42:10Z</dc:date>
    <item>
      <title>on increasing data segment size</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/on-increasing-data-segment-size/m-p/2763658#M894397</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;What is the effect of increasing the data segment size on performance of a heavy loaded server ? What is the optimum value suggested ? Is it advicable to use EXEC_MAGIC and SHMEM_MAGIC ?&lt;BR /&gt;&lt;BR /&gt;Thanks and Regards&lt;BR /&gt;Vishal</description>
      <pubDate>Mon, 15 Jul 2002 10:27:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/on-increasing-data-segment-size/m-p/2763658#M894397</guid>
      <dc:creator>Vishal Augustine</dc:creator>
      <dc:date>2002-07-15T10:27:16Z</dc:date>
    </item>
    <item>
      <title>Re: on increasing data segment size</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/on-increasing-data-segment-size/m-p/2763659#M894398</link>
      <description>It depends on what kind of bottleneck you have. What ave you done to determine that?&lt;BR /&gt;The parameter only limits the mount of "data" each process can allocate so my guess is it won't help.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Trond</description>
      <pubDate>Mon, 15 Jul 2002 10:45:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/on-increasing-data-segment-size/m-p/2763659#M894398</guid>
      <dc:creator>Trond Haugen</dc:creator>
      <dc:date>2002-07-15T10:45:14Z</dc:date>
    </item>
    <item>
      <title>Re: on increasing data segment size</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/on-increasing-data-segment-size/m-p/2763660#M894399</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;malloc is failing at times. This means the server is heavily loaded. The ulimit of data segment is 65536 KB. I believe increasing the data segment size should solve the problem. Using EXEC_MAGIC flag while linking will also solve the issue. Am I right ? What I don't know is its impact on the performance of the server (both on the machine and individual server-processes)&lt;BR /&gt;&lt;BR /&gt;Thanks and Regards&lt;BR /&gt;Vishal&lt;BR /&gt;</description>
      <pubDate>Tue, 16 Jul 2002 04:47:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/on-increasing-data-segment-size/m-p/2763660#M894399</guid>
      <dc:creator>Vishal Augustine</dc:creator>
      <dc:date>2002-07-16T04:47:48Z</dc:date>
    </item>
    <item>
      <title>Re: on increasing data segment size</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/on-increasing-data-segment-size/m-p/2763661#M894400</link>
      <description>malloc failing does not indicate a heavily loaded server. malloc will fail for three basic reasons: the request exceeds the kernel fence: maxdsiz, or the reuest exceeds 940 megs, the limit for standard executables (where multiple quadrant maps are not available, ie, the MAGIC executables), or you are out of swap space. Unfortunately, the program cannot determine the real reason, so you have to investigate each scenario.&lt;BR /&gt;&lt;BR /&gt;Start with maxdsiz. The default is 67 megs which is tpyically way too restrictive. Change this fence value to 940 megs for standard programs, or bump it up to 1750 megs if you plan on creating MAGIC executables.&lt;BR /&gt;&lt;BR /&gt;Then run swapinfo -tam when malloc fails to see if most of the swap space is used (not just reserved). If all is well, then use chatr to change you executable(s) to map quadrants 1 and 2 together, thus allowing up to apx 1750 megs in the data area.&lt;BR /&gt;&lt;BR /&gt;The details are in: /usr/share/doc in the two whitepapers: mem_mgt and proc_mgt.</description>
      <pubDate>Tue, 16 Jul 2002 11:11:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/on-increasing-data-segment-size/m-p/2763661#M894400</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2002-07-16T11:11:40Z</dc:date>
    </item>
    <item>
      <title>Re: on increasing data segment size</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/on-increasing-data-segment-size/m-p/2763662#M894401</link>
      <description>Jut to add to Bill's answer. You should not experience any change in performance when doing these changes. But as always with tuning only doing it will tell for sure.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Trond</description>
      <pubDate>Wed, 17 Jul 2002 05:42:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/on-increasing-data-segment-size/m-p/2763662#M894401</guid>
      <dc:creator>Trond Haugen</dc:creator>
      <dc:date>2002-07-17T05:42:10Z</dc:date>
    </item>
  </channel>
</rss>

