<?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: Model Manger performance in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/Model-Manger-performance/m-p/429571#M12005</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/62003"&gt;@Riana&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;the slowness depends on many things, but I would make my first bet that it is slow just due to Java - JVM boundaries that are reached.&lt;/P&gt;
&lt;P&gt;Here is what I would do, for starters:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;0. Check if any non-SAS service/process is consuming your server resources. If any, manage it to give resources back to SAS.&lt;/P&gt;
&lt;P&gt;1 . I would restart the middle tier, and before starting the services, I would clean/archive the temporary files (SASServerX_X\work \temp and \log)&lt;/P&gt;
&lt;P&gt;2. Once it is restarted, if performance is still slow, I would recommend you to clean/archive your audit tables in WIP database (&amp;nbsp;&lt;A href="http://support.sas.com/kb/58/599.html" target="_blank"&gt;http://support.sas.com/kb/58/599.html&lt;/A&gt; ), then restart the middle-tier.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 22 Jan 2018 09:38:43 GMT</pubDate>
    <dc:creator>JuanS_OCS</dc:creator>
    <dc:date>2018-01-22T09:38:43Z</dc:date>
    <item>
      <title>Model Manger performance</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Model-Manger-performance/m-p/429562#M12003</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;If SAS Model Manager is slow, what should be checked? Or what are those that can affect the performance?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jan 2018 09:11:46 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Model-Manger-performance/m-p/429562#M12003</guid>
      <dc:creator>Riana</dc:creator>
      <dc:date>2018-01-22T09:11:46Z</dc:date>
    </item>
    <item>
      <title>Re: Model Manger performance</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Model-Manger-performance/m-p/429571#M12005</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/62003"&gt;@Riana&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;the slowness depends on many things, but I would make my first bet that it is slow just due to Java - JVM boundaries that are reached.&lt;/P&gt;
&lt;P&gt;Here is what I would do, for starters:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;0. Check if any non-SAS service/process is consuming your server resources. If any, manage it to give resources back to SAS.&lt;/P&gt;
&lt;P&gt;1 . I would restart the middle tier, and before starting the services, I would clean/archive the temporary files (SASServerX_X\work \temp and \log)&lt;/P&gt;
&lt;P&gt;2. Once it is restarted, if performance is still slow, I would recommend you to clean/archive your audit tables in WIP database (&amp;nbsp;&lt;A href="http://support.sas.com/kb/58/599.html" target="_blank"&gt;http://support.sas.com/kb/58/599.html&lt;/A&gt; ), then restart the middle-tier.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jan 2018 09:38:43 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Model-Manger-performance/m-p/429571#M12005</guid>
      <dc:creator>JuanS_OCS</dc:creator>
      <dc:date>2018-01-22T09:38:43Z</dc:date>
    </item>
  </channel>
</rss>

