<?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: Default memsize 2G, way too smal…why? in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/Default-memsize-2G-way-too-smal-why/m-p/914320#M27968</link>
    <description>&lt;P&gt;One reason is in the documentation for the MEMSIZE option:&lt;/P&gt;
&lt;BLOCKQUOTE&gt;
&lt;DIV class="xis-eDocBody"&gt;
&lt;DIV class="xis-refDictEntry"&gt;
&lt;DIV class="xis-details"&gt;
&lt;DIV id="p0rd8ssdx7p6p1n10w46m1g45um2" class="xis-topicContent"&gt;
&lt;DIV id="n0ur53jc7jdsbln1x5xym1f5vrgz" class="xis-note"&gt;&lt;SPAN class="xis-noteGenText"&gt;Note: &lt;/SPAN&gt;Setting &lt;FONT style="background-color: #fcdec0;"&gt;MEMSIZE&lt;/FONT&gt; to MAX is reasonable only if consumers of large amounts of memory are not likely to become active after SAS has started. For example, if multiple instances of SAS are running concurrently, and all of these instances are started with a &lt;FONT style="background-color: #fcdec0;"&gt;MEMSIZE&lt;/FONT&gt; value of MAX, one or more of these instances can encounter out of memory conditions, or, the operating system can run out of available paging space.&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;You may not do it but it is very easy to have multiple SAS sessions run at the same time, especially if running BATCH programs. I have run as many as 25 batch programs concurrently (but not with such a large Memsize setting).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have the luxury of not working with "large" data sets so have never actually run into a memory limitation. YMMV.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 02 Feb 2024 20:51:39 GMT</pubDate>
    <dc:creator>ballardw</dc:creator>
    <dc:date>2024-02-02T20:51:39Z</dc:date>
    <item>
      <title>Default memsize 2G, way too smal…why?</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Default-memsize-2G-way-too-smal-why/m-p/914286#M27966</link>
      <description>It’s a simple question really…why is the default memsize option 2G when realistically if you’re working w/any sizeable dataset or doing memory intensive procedures like multiple imputation you will need way more memory than this? Also, realistically (hopefully) most ppl are operating systems w/at least 16G of RAM, couldnt the default memsize reasonably be increased to at LEAST 4G if not bigger? I just set mine to max, but wondering why default is so low.</description>
      <pubDate>Fri, 02 Feb 2024 19:30:26 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Default-memsize-2G-way-too-smal-why/m-p/914286#M27966</guid>
      <dc:creator>zfusfeld</dc:creator>
      <dc:date>2024-02-02T19:30:26Z</dc:date>
    </item>
    <item>
      <title>Re: Default memsize 2G, way too smal…why?</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Default-memsize-2G-way-too-smal-why/m-p/914320#M27968</link>
      <description>&lt;P&gt;One reason is in the documentation for the MEMSIZE option:&lt;/P&gt;
&lt;BLOCKQUOTE&gt;
&lt;DIV class="xis-eDocBody"&gt;
&lt;DIV class="xis-refDictEntry"&gt;
&lt;DIV class="xis-details"&gt;
&lt;DIV id="p0rd8ssdx7p6p1n10w46m1g45um2" class="xis-topicContent"&gt;
&lt;DIV id="n0ur53jc7jdsbln1x5xym1f5vrgz" class="xis-note"&gt;&lt;SPAN class="xis-noteGenText"&gt;Note: &lt;/SPAN&gt;Setting &lt;FONT style="background-color: #fcdec0;"&gt;MEMSIZE&lt;/FONT&gt; to MAX is reasonable only if consumers of large amounts of memory are not likely to become active after SAS has started. For example, if multiple instances of SAS are running concurrently, and all of these instances are started with a &lt;FONT style="background-color: #fcdec0;"&gt;MEMSIZE&lt;/FONT&gt; value of MAX, one or more of these instances can encounter out of memory conditions, or, the operating system can run out of available paging space.&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;You may not do it but it is very easy to have multiple SAS sessions run at the same time, especially if running BATCH programs. I have run as many as 25 batch programs concurrently (but not with such a large Memsize setting).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have the luxury of not working with "large" data sets so have never actually run into a memory limitation. YMMV.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 02 Feb 2024 20:51:39 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Default-memsize-2G-way-too-smal-why/m-p/914320#M27968</guid>
      <dc:creator>ballardw</dc:creator>
      <dc:date>2024-02-02T20:51:39Z</dc:date>
    </item>
    <item>
      <title>Re: Default memsize 2G, way too smal…why?</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Default-memsize-2G-way-too-smal-why/m-p/914355#M27969</link>
      <description>&lt;P&gt;In most cases, SAS is used in a client/server environment, where multiple SAS processes will run concurrently on the server and have to share the available memory.&lt;/P&gt;
&lt;P&gt;On the SAS server I administered before retiring, the workspace server had a memsize of 512M defined, as we had to accommodate up to 50 concurrent workspace servers, the whole EBI backend (Java is a massive resource hog!), and the batch jobs with 128G of physical memory.&lt;/P&gt;</description>
      <pubDate>Fri, 02 Feb 2024 22:28:20 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Default-memsize-2G-way-too-smal-why/m-p/914355#M27969</guid>
      <dc:creator>Kurt_Bremser</dc:creator>
      <dc:date>2024-02-02T22:28:20Z</dc:date>
    </item>
    <item>
      <title>Re: Default memsize 2G, way too smal…why?</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Default-memsize-2G-way-too-smal-why/m-p/914357#M27970</link>
      <description>&lt;P&gt;You need to remember that SAS runs not just on PCs, but on also on large servers where memory is shared across many users, so having a fairly low default setting is a good compromise.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The default 2GB setting was increased a while back I seem to recall. On our main SAS server I've currently got it set to 6GB and that appears to be fine for most users.&lt;/P&gt;</description>
      <pubDate>Fri, 02 Feb 2024 22:37:05 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Default-memsize-2G-way-too-smal-why/m-p/914357#M27970</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2024-02-02T22:37:05Z</dc:date>
    </item>
  </channel>
</rss>

