<?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: Application Visibility impact on CPU in Access Points - Indoor and Outdoor</title>
    <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Application-Visibility-impact-on-CPU/m-p/34612#M9790</link>
    <description>&lt;P&gt;It's true that Application Visibility will add to your ZD resource utilization.&lt;/P&gt;&lt;P&gt;It has about the same level of resource consumption as Real Time Monitoring.&lt;/P&gt;&lt;P&gt;Both are to be avoided in a more taxing environment, but your ZD w/8 APs&lt;/P&gt;&lt;P&gt;averaging 50 users would be about medium level usage, so evaluate and use the&lt;/P&gt;&lt;P&gt;feature if needed/helpful.&lt;/P&gt;</description>
    <pubDate>Fri, 07 Aug 2015 18:17:02 GMT</pubDate>
    <dc:creator>michael_brado</dc:creator>
    <dc:date>2015-08-07T18:17:02Z</dc:date>
    <item>
      <title>Application Visibility impact on CPU</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Application-Visibility-impact-on-CPU/m-p/34611#M9789</link>
      <description>&lt;P&gt;Does anyone has some
experience with the Application Visibility feature?&lt;/P&gt;

&lt;P&gt;How much does it impact
an AP CPU utilization / ZD CPU utilization?&lt;/P&gt;

&lt;P&gt;AP – ZF7982, R700, R710&lt;/P&gt;

&lt;P&gt;ZD – ZD3k&lt;/P&gt;

&lt;P&gt;The average load per AP&amp;nbsp;in
terms of clients: &amp;nbsp;50&lt;/P&gt;

&lt;P&gt;With only 8 APs the ZD3k
(9.12) shows CPU 40% and the webUI seems rather slow. I don’t know if it is
related to this feature being enabled or not.&lt;/P&gt;

Thanks.&lt;BR /&gt;&lt;BR /&gt;Alex</description>
      <pubDate>Fri, 07 Aug 2015 09:03:29 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Application-Visibility-impact-on-CPU/m-p/34611#M9789</guid>
      <dc:creator>alexandra_frinc</dc:creator>
      <dc:date>2015-08-07T09:03:29Z</dc:date>
    </item>
    <item>
      <title>Re: Application Visibility impact on CPU</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Application-Visibility-impact-on-CPU/m-p/34612#M9790</link>
      <description>&lt;P&gt;It's true that Application Visibility will add to your ZD resource utilization.&lt;/P&gt;&lt;P&gt;It has about the same level of resource consumption as Real Time Monitoring.&lt;/P&gt;&lt;P&gt;Both are to be avoided in a more taxing environment, but your ZD w/8 APs&lt;/P&gt;&lt;P&gt;averaging 50 users would be about medium level usage, so evaluate and use the&lt;/P&gt;&lt;P&gt;feature if needed/helpful.&lt;/P&gt;</description>
      <pubDate>Fri, 07 Aug 2015 18:17:02 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Application-Visibility-impact-on-CPU/m-p/34612#M9790</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2015-08-07T18:17:02Z</dc:date>
    </item>
    <item>
      <title>Re: Application Visibility impact on CPU</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Application-Visibility-impact-on-CPU/m-p/34613#M9791</link>
      <description>Thank you for your answer Michael. &lt;BR /&gt;&lt;BR /&gt;To follow up: After disabling the Application Visibility we saw a 10% decrease in the ZD3k CPU.&lt;BR /&gt;However, the ZD3k webUI was still slow with 9.12.0.0.336 and the CPU 30-40% (even with no APs).&lt;BR /&gt;&lt;BR /&gt;On ZD5k 9.12.0.0.336 works fine (max ZD CPU 5%).</description>
      <pubDate>Fri, 28 Aug 2015 12:49:51 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Application-Visibility-impact-on-CPU/m-p/34613#M9791</guid>
      <dc:creator>alexandra_frinc</dc:creator>
      <dc:date>2015-08-28T12:49:51Z</dc:date>
    </item>
  </channel>
</rss>

