<?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: Understanding Efficiency Trade-offs? in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/Understanding-Efficiency-Trade-offs/m-p/86442#M18514</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would definitely recommend reviewing the papers Cynthia has provided as they will provide a lot more context and information than the following.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) This is most likely a reference to data set compression, using the COMPRESS option, this decreases the size of the dataset on disk and in turn the number of I/O operations required to access it.&amp;nbsp; This increases CPU Usage because when reading or writing compressed data there is the extra step to perform the decompression or compression of said data.&amp;nbsp; I do not believe there is a real impact to memory with this.&lt;/P&gt;&lt;P&gt;2) I will take a wild guess here and say you are referring to the SORTSIZE option in PROC SORT, but similar memory size options will relate somewhat.&amp;nbsp; By increasing the allowable memory to a sort you can reduce the number of I/O operations performed of the utility files because larger portions of the file can be handled in memory at a time.&amp;nbsp; I/O is typically the most time-expensive operation.&amp;nbsp; SASFILE can also help reduce I/O operations for steps that involve reading files multiple times, as this will place the contents of the file into memory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FULLSTIMER option is good to use and will help you see where processes are spending their time and what the costs of various tweaks are:&lt;/P&gt;&lt;P&gt;&lt;A class="active_link" href="http://support.sas.com/rnd/scalability/tools/fullstim/index.html"&gt;http://support.sas.com/rnd/scalability/tools/fullstim/index.html&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 17 Apr 2012 18:46:36 GMT</pubDate>
    <dc:creator>FriedEgg</dc:creator>
    <dc:date>2012-04-17T18:46:36Z</dc:date>
    <item>
      <title>Understanding Efficiency Trade-offs?</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Understanding-Efficiency-Trade-offs/m-p/86440#M18512</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Everyone,&lt;/P&gt;&lt;P&gt;Can anyone please explain the Efficiency Trade-offs in SAS. I am having hard time&lt;/P&gt;&lt;P&gt;understanding the above concepts.Following are two questions:&lt;/P&gt;&lt;P&gt;1)How decrease in the size of a SAS Dataset can result in an increase in CPU Usage?&lt;/P&gt;&lt;P&gt;2)How decrease in the number of I/O operations comes at the expense of Increased&lt;/P&gt;&lt;P&gt;memory usage?&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;John&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Apr 2012 15:49:05 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Understanding-Efficiency-Trade-offs/m-p/86440#M18512</guid>
      <dc:creator>john83</dc:creator>
      <dc:date>2012-04-17T15:49:05Z</dc:date>
    </item>
    <item>
      <title>Re: Understanding Efficiency Trade-offs?</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Understanding-Efficiency-Trade-offs/m-p/86441#M18513</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;BR /&gt;Hi:&lt;/P&gt;&lt;P&gt;&amp;nbsp; Efficiency is always a trade-off -- decreasing one resource can, and frequently does, increase another resource. This is a good place to start in reading about efficiency techniques:&lt;/P&gt;&lt;P&gt;&lt;A href="http://www2.sas.com/proceedings/forum2007/042-2007.pdf" title="http://www2.sas.com/proceedings/forum2007/042-2007.pdf"&gt;http://www2.sas.com/proceedings/forum2007/042-2007.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; And a Google search on SAS Efficiency reveals other papers, like these:&lt;/P&gt;&lt;P&gt;&lt;A class="active_link" href="http://www.nesug.org/Proceedings/nesug11/ds/ds02.pdf" title="http://www.nesug.org/Proceedings/nesug11/ds/ds02.pdf"&gt;http://www.nesug.org/Proceedings/nesug11/ds/ds02.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.mwsug.org/proceedings/2009/how/MWSUG-2009-H06.pdf" title="http://www.mwsug.org/proceedings/2009/how/MWSUG-2009-H06.pdf"&gt;http://www.mwsug.org/proceedings/2009/how/MWSUG-2009-H06.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; I'm sure you can find more.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cynthia&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Apr 2012 16:04:01 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Understanding-Efficiency-Trade-offs/m-p/86441#M18513</guid>
      <dc:creator>Cynthia_sas</dc:creator>
      <dc:date>2012-04-17T16:04:01Z</dc:date>
    </item>
    <item>
      <title>Re: Understanding Efficiency Trade-offs?</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Understanding-Efficiency-Trade-offs/m-p/86442#M18514</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would definitely recommend reviewing the papers Cynthia has provided as they will provide a lot more context and information than the following.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) This is most likely a reference to data set compression, using the COMPRESS option, this decreases the size of the dataset on disk and in turn the number of I/O operations required to access it.&amp;nbsp; This increases CPU Usage because when reading or writing compressed data there is the extra step to perform the decompression or compression of said data.&amp;nbsp; I do not believe there is a real impact to memory with this.&lt;/P&gt;&lt;P&gt;2) I will take a wild guess here and say you are referring to the SORTSIZE option in PROC SORT, but similar memory size options will relate somewhat.&amp;nbsp; By increasing the allowable memory to a sort you can reduce the number of I/O operations performed of the utility files because larger portions of the file can be handled in memory at a time.&amp;nbsp; I/O is typically the most time-expensive operation.&amp;nbsp; SASFILE can also help reduce I/O operations for steps that involve reading files multiple times, as this will place the contents of the file into memory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FULLSTIMER option is good to use and will help you see where processes are spending their time and what the costs of various tweaks are:&lt;/P&gt;&lt;P&gt;&lt;A class="active_link" href="http://support.sas.com/rnd/scalability/tools/fullstim/index.html"&gt;http://support.sas.com/rnd/scalability/tools/fullstim/index.html&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Apr 2012 18:46:36 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Understanding-Efficiency-Trade-offs/m-p/86442#M18514</guid>
      <dc:creator>FriedEgg</dc:creator>
      <dc:date>2012-04-17T18:46:36Z</dc:date>
    </item>
  </channel>
</rss>

