<?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: Oracle SGA Spans Multiple Segments in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/oracle-sga-spans-multiple-segments/m-p/3801004#M782415</link>
    <description>This is referring to an old data point that the Oracle database could keep only so many data segments accessible at once.  If my memory is correct (and this could be wrong, but the point would be the same) it was 5 (maybe 7?). The system could simultaneously read/write/update 5(7?) memory segments at once, if you had more than this than those other segments would have to be turned on live, and then some other one would go cold .  This would make your requests kind of queue up behind this switching mechanism.  &lt;BR /&gt;&lt;BR /&gt;Regardless, I would say that it would certainly be less overhead to let Oracle manage its shared memory segments in as few as possible.  You should always try to do them in as few as possible, by making sure that shmmax is bigger than the SGA you're trying to stand up, when and where possible.</description>
    <pubDate>Tue, 06 Jun 2006 13:09:23 GMT</pubDate>
    <dc:creator>TwoProc</dc:creator>
    <dc:date>2006-06-06T13:09:23Z</dc:date>
    <item>
      <title>Oracle SGA Spans Multiple Segments</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/oracle-sga-spans-multiple-segments/m-p/3801002#M782413</link>
      <description>The HP-UX Performance Cookbook says that performance is negatively impacted when Oracle's SGA spans multiple segments.  Could someone provide a specific example of this happening and the performance impact?</description>
      <pubDate>Tue, 06 Jun 2006 11:26:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/oracle-sga-spans-multiple-segments/m-p/3801002#M782413</guid>
      <dc:creator>spex</dc:creator>
      <dc:date>2006-06-06T11:26:32Z</dc:date>
    </item>
    <item>
      <title>Re: Oracle SGA Spans Multiple Segments</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/oracle-sga-spans-multiple-segments/m-p/3801003#M782414</link>
      <description>They are referring to cases where the tunable shmmax is set too small (e.g. 1GB) but the size of the SGA is larger (e.g 5GB). In that case, Oracle shmget()'s multiple segments (at least 5 in this case) to build the SGA but this fragmented access is less efficient than 1 contiguous memory area. (I assume that you are referring to 64-bit HP-UX and Oracle.) &lt;BR /&gt;&lt;BR /&gt;If you wish to measure this effect then reduce shmmax and leave your SGA large. Do an ipcs -ma and you will see multiple shared memory segents associated with the same Oracle instance. Do some benchmarks comparing the performance of 1 large vs multiple small segments.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 06 Jun 2006 12:25:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/oracle-sga-spans-multiple-segments/m-p/3801003#M782414</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2006-06-06T12:25:25Z</dc:date>
    </item>
    <item>
      <title>Re: Oracle SGA Spans Multiple Segments</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/oracle-sga-spans-multiple-segments/m-p/3801004#M782415</link>
      <description>This is referring to an old data point that the Oracle database could keep only so many data segments accessible at once.  If my memory is correct (and this could be wrong, but the point would be the same) it was 5 (maybe 7?). The system could simultaneously read/write/update 5(7?) memory segments at once, if you had more than this than those other segments would have to be turned on live, and then some other one would go cold .  This would make your requests kind of queue up behind this switching mechanism.  &lt;BR /&gt;&lt;BR /&gt;Regardless, I would say that it would certainly be less overhead to let Oracle manage its shared memory segments in as few as possible.  You should always try to do them in as few as possible, by making sure that shmmax is bigger than the SGA you're trying to stand up, when and where possible.</description>
      <pubDate>Tue, 06 Jun 2006 13:09:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/oracle-sga-spans-multiple-segments/m-p/3801004#M782415</guid>
      <dc:creator>TwoProc</dc:creator>
      <dc:date>2006-06-06T13:09:23Z</dc:date>
    </item>
    <item>
      <title>Re: Oracle SGA Spans Multiple Segments</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/oracle-sga-spans-multiple-segments/m-p/3801005#M782416</link>
      <description>A. Clay &amp;amp; John, &lt;BR /&gt;&lt;BR /&gt;Thank you for the insight.  Yes, 64-bit HP-UX 11.00 and Oracle 8i on this box.  &lt;BR /&gt;&lt;BR /&gt;# kmtune |grep shmmax&lt;BR /&gt;shmmax               1073741824&lt;BR /&gt;&lt;BR /&gt;# ipcs -ma |awk '/oracle/ {print $10}'&lt;BR /&gt;1073741824&lt;BR /&gt;564658176 &lt;BR /&gt;579985408&lt;BR /&gt;&lt;BR /&gt;The first two lines are the buffer cache, and the third is the remainder of the pools.&lt;BR /&gt;&lt;BR /&gt;I won't be able to reboot for some time, so I was hoping someone could provide specific before and after figures from a similar adjustment (SGA in three segments with shmmax set to 1GB to one segment with shmmax at, say, 3GB).  I'm basically wondering if it's worth recompiling just for this.</description>
      <pubDate>Tue, 06 Jun 2006 13:26:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/oracle-sga-spans-multiple-segments/m-p/3801005#M782416</guid>
      <dc:creator>spex</dc:creator>
      <dc:date>2006-06-06T13:26:58Z</dc:date>
    </item>
    <item>
      <title>Re: Oracle SGA Spans Multiple Segments</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/oracle-sga-spans-multiple-segments/m-p/3801006#M782417</link>
      <description>I'd do it, but it's not urgent.  Do it at your next scheduled reboot/patch/etc.</description>
      <pubDate>Tue, 06 Jun 2006 13:49:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/oracle-sga-spans-multiple-segments/m-p/3801006#M782417</guid>
      <dc:creator>TwoProc</dc:creator>
      <dc:date>2006-06-06T13:49:18Z</dc:date>
    </item>
  </channel>
</rss>

