<?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 Tips on making programs more efficient  -  server gives warning:  physical memory usage too high in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/Tips-on-making-programs-more-efficient-server-gives-warning/m-p/23508#M3901</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We use a server with operating system Windows Server 2008 Standard, 64 bit.&amp;nbsp; SAS for Windows is loaded as release 9.2,&amp;nbsp; 64 bit version.&lt;/P&gt;&lt;P&gt;Our Information Technology department is not well versed on SAS and the needs of the SAS System.&amp;nbsp; There is a monitoring system in place and it keeps giving us these warnings:&amp;nbsp; "Spectrum ALARM - Physical Memory Usage Too High".&amp;nbsp;&amp;nbsp; Has anybody ever dealt with this issue ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Some have suggested that the problem may be a few programmers, new to SAS,&amp;nbsp; running code that is not efficient, thus, using up a lot of physical memory.&amp;nbsp;&amp;nbsp; My question is What tips can I give to the new guys about how to write more efficient code, without sending them off to a SAS training course?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 06 Mar 2012 19:24:12 GMT</pubDate>
    <dc:creator>chandler</dc:creator>
    <dc:date>2012-03-06T19:24:12Z</dc:date>
    <item>
      <title>Tips on making programs more efficient  -  server gives warning:  physical memory usage too high</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Tips-on-making-programs-more-efficient-server-gives-warning/m-p/23508#M3901</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We use a server with operating system Windows Server 2008 Standard, 64 bit.&amp;nbsp; SAS for Windows is loaded as release 9.2,&amp;nbsp; 64 bit version.&lt;/P&gt;&lt;P&gt;Our Information Technology department is not well versed on SAS and the needs of the SAS System.&amp;nbsp; There is a monitoring system in place and it keeps giving us these warnings:&amp;nbsp; "Spectrum ALARM - Physical Memory Usage Too High".&amp;nbsp;&amp;nbsp; Has anybody ever dealt with this issue ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Some have suggested that the problem may be a few programmers, new to SAS,&amp;nbsp; running code that is not efficient, thus, using up a lot of physical memory.&amp;nbsp;&amp;nbsp; My question is What tips can I give to the new guys about how to write more efficient code, without sending them off to a SAS training course?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Mar 2012 19:24:12 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Tips-on-making-programs-more-efficient-server-gives-warning/m-p/23508#M3901</guid>
      <dc:creator>chandler</dc:creator>
      <dc:date>2012-03-06T19:24:12Z</dc:date>
    </item>
    <item>
      <title>Re: Tips on making programs more efficient  -  server gives warning:  physical memory usage too high</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Tips-on-making-programs-more-efficient-server-gives-warning/m-p/23509#M3902</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There are a number of places that new users can use a lot of memory.&amp;nbsp; This is only a guess at what might apply in your shop.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In a DATA step, new users have to realize that these steps are different:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;data new (keep=a list of final variables);&lt;/P&gt;&lt;P&gt;set old;&lt;/P&gt;&lt;P&gt;** calculations;&lt;/P&gt;&lt;P&gt;run;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;data new (keep=a list of final variables);&lt;/P&gt;&lt;P&gt;set old (keep=just the variables I need to read in);&lt;/P&gt;&lt;P&gt;** calculations; &lt;/P&gt;&lt;P&gt;run;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The first step reads in all of the variables.&amp;nbsp; If you have a gazillion variables, that can consume memory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In PROC FREQ, the software tracks all combinations.&amp;nbsp; So this table would require enormous amounts of memory:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;proc freq data=purchases;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; tables credit_card_no * date / noprint out=counts;&lt;/P&gt;&lt;P&gt;run;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In PROC MEANS (or PROC SUMMARY), the CLASS statement tracks all levels at once.&amp;nbsp; That can also consume memory:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;proc summary data=purchases;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; class credit_card_no;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; var amount;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; output ...&lt;/P&gt;&lt;P&gt;run;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But there's no guarantee that the fault lies with the users.&amp;nbsp; And here at the discussion forum, we don't really have much of a clue as to what the users are actually doing.&amp;nbsp; These are just some pitfalls using commonplace tools.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Good luck.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Mar 2012 20:06:04 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Tips-on-making-programs-more-efficient-server-gives-warning/m-p/23509#M3902</guid>
      <dc:creator>Astounding</dc:creator>
      <dc:date>2012-03-06T20:06:04Z</dc:date>
    </item>
    <item>
      <title>Tips on making programs more efficient  -  server gives warning:  physical memory usage too high</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Tips-on-making-programs-more-efficient-server-gives-warning/m-p/23510#M3903</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can setup restrictions to memory consumption by using SAS system options.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Inspect you current setup by running the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;proc options group=memory; run;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;you can limit the memory SAS will use by altering these options&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here are links to additional information about the memory options: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;TABLE border="1" cellpadding="6" cellspacing="0" style="line-height: 1.25em; font-family: arial, 'Arial Unicode MS', geneva, 'Lucida Grande', sans-serif; color: #000000; background-color: #ffffff;"&gt;&lt;TBODY style="line-height: 1.25em; font-family: inherit;"&gt;&lt;TR style="line-height: 1.25em; font-family: inherit; vertical-align: top;" valign="top"&gt;&lt;TD width="24%"&gt;System administration: Memory&lt;/TD&gt;&lt;TD width="24%"&gt;&lt;A href="http://support.sas.com/documentation/cdl/en/lrdict/64316/HTML/default/a000279221.htm" style="line-height: 1.25em; color: #000066;"&gt;SORTSIZE= System Option&lt;/A&gt;&lt;/TD&gt;&lt;TD width="49%"&gt;Specifies the amount of memory that is available to the SORT procedure.&lt;/TD&gt;&lt;/TR&gt;&lt;TR style="line-height: 1.25em; font-family: inherit; vertical-align: top;" valign="top"&gt;&lt;TD width="24%"&gt;&lt;BR /&gt;&lt;/TD&gt;&lt;TD width="24%"&gt;&lt;A href="http://support.sas.com/documentation/cdl/en/lrdict/64316/HTML/default/a000606560.htm" style="line-height: 1.25em; color: #000066;"&gt;SUMSIZE= System Option&lt;/A&gt;&lt;/TD&gt;&lt;TD width="49%"&gt;Specifies a limit on the amount of memory that is available for data summarization procedures when class variables are active.&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0.7em; line-height: 1.25em; font-family: arial, 'Arial Unicode MS', geneva, 'Lucida Grande', sans-serif; color: #000000;"&gt;MEMSIZE System Option under &lt;A href="http://support.sas.com/documentation/cdl/en/hostwin/63285/HTML/default/win-sysop-memsize.htm" style="line-height: 1.25em; color: #000066;" target="_top"&gt;Windows&lt;/A&gt;, &lt;A href="http://support.sas.com/documentation/cdl/en/hostunx/61879/HTML/default/o-m2.htm" style="line-height: 1.25em; color: #000066;" target="_top"&gt;UNIX&lt;/A&gt;, &lt;A href="http://support.sas.com/documentation/cdl/en/hostvms/62450/HTML/default/alp-sysops-memsize.htm" style="line-height: 1.25em; color: #000066;" target="_top"&gt;OpenVMS&lt;/A&gt;, &lt;A href="http://support.sas.com/documentation/cdl/en/hosto390/61886/HTML/default/a000216991.htm" style="line-height: 1.25em; color: #000066;" target="_top"&gt;z/OS&lt;/A&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0.7em; line-height: 1.25em; font-family: arial, 'Arial Unicode MS', geneva, 'Lucida Grande', sans-serif; color: #000000;"&gt;&lt;A name="a002899897" style="line-height: 1.25em; font-family: inherit;"&gt;&lt;/A&gt;REALMEMSIZE System Option under&lt;A href="http://support.sas.com/documentation/cdl/en/hostwin/63285/HTML/default/win-sysop-realmemsize.htm" style="line-height: 1.25em; color: #000066;" target="_top"&gt; Windows&lt;/A&gt;, &lt;A href="http://support.sas.com/documentation/cdl/en/hostunx/61879/HTML/default/a001677204.htm" style="line-height: 1.25em; color: #000066;" target="_top"&gt;UNIX&lt;/A&gt;, &lt;A href="http://support.sas.com/documentation/cdl/en/hostvms/62450/HTML/default/alp-sysop-realmemsize.htm" style="line-height: 1.25em; color: #000066;" target="_top"&gt;OpenVMS&lt;/A&gt;, &lt;A href="http://support.sas.com/documentation/cdl/en/hosto390/61886/HTML/default/a001625868.htm" style="line-height: 1.25em; color: #000066;" target="_top"&gt;z/OS&lt;/A&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0.7em; line-height: 1.25em; font-family: arial, 'Arial Unicode MS', geneva, 'Lucida Grande', sans-serif; color: #000000;"&gt;&lt;A href="http://support.sas.com/documentation/cdl/en/hostwin/63285/HTML/default/win-sysop-memmaxsz.htm" style="line-height: 16px; font-family: arial, 'Arial Unicode MS', geneva, 'Lucida Grande', sans-serif; color: #000066; background-color: #ffffff;"&gt;MEMMAXSZ System Option: Windows&lt;/A&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0.7em; line-height: 1.25em; font-family: arial, 'Arial Unicode MS', geneva, 'Lucida Grande', sans-serif; color: #000000;"&gt;&lt;A href="http://support.sas.com/documentation/cdl/en/hostwin/63285/HTML/default/win-sysop-memlib.htm" style="line-height: 16px; font-family: arial, 'Arial Unicode MS', geneva, 'Lucida Grande', sans-serif; color: #000066; background-color: #ffffff;"&gt;MEMLIB System Option: Windows&lt;/A&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0.7em; line-height: 1.25em; font-family: arial, 'Arial Unicode MS', geneva, 'Lucida Grande', sans-serif; color: #000000;"&gt;&lt;A class="active_link" href="http://support.sas.com/documentation/cdl/en/hostwin/63285/HTML/default/win-sysop-memcache.htm" style="line-height: 16px; font-family: arial, 'Arial Unicode MS', geneva, 'Lucida Grande', sans-serif; color: #000066; background-color: #ffffff;"&gt;MEMCACHE System Option: Windows&lt;/A&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0.7em; line-height: 1.25em; font-family: arial, 'Arial Unicode MS', geneva, 'Lucida Grande', sans-serif; color: #000000;"&gt;&lt;A href="http://support.sas.com/documentation/cdl/en/hostwin/63285/HTML/default/win-sysop-loadmemsize.htm" style="line-height: 16px; font-family: arial, 'Arial Unicode MS', geneva, 'Lucida Grande', sans-serif; color: #000066; background-color: #ffffff;"&gt;LOADMEMSIZE System Option: Windows&lt;/A&gt;&lt;/P&gt;&lt;P style="margin-bottom: 0.7em; line-height: 1.25em; font-family: arial, 'Arial Unicode MS', geneva, 'Lucida Grande', sans-serif; color: #000000;"&gt;&lt;A href="http://support.sas.com/documentation/cdl/en/hostwin/63285/HTML/default/win-sysop-memblksz.htm" style="line-height: 16px; font-family: arial, 'Arial Unicode MS', geneva, 'Lucida Grande', sans-serif; color: #000066; background-color: #ffffff;"&gt;MEMBLKSZ System Option: Windows&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Be careful when setting the options as you can cause errors to occur by setting options too low and you can also dramatically increase disk operations and decrease performance.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Mar 2012 20:20:16 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Tips-on-making-programs-more-efficient-server-gives-warning/m-p/23510#M3903</guid>
      <dc:creator>FriedEgg</dc:creator>
      <dc:date>2012-03-06T20:20:16Z</dc:date>
    </item>
  </channel>
</rss>

