<?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: CPU Performances issues when running input powershell scripts in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/CPU-Performances-issues-when-running-input-powershell-scripts/m-p/117496#M1391</link>
    <description>&lt;P&gt;Yes, do something else useful on the server.  Why do you care that CPU goes to 80%?  If the server is sitting there totally idle (CPU=0%), then it makes perfect sense for the OS/scheduler to allot what would normally be excessive resources to a low priority task.  I would expect and desire it to do exactly that; why do you expect otherwise?&lt;/P&gt;</description>
    <pubDate>Sun, 24 May 2015 21:51:32 GMT</pubDate>
    <dc:creator>woodcock</dc:creator>
    <dc:date>2015-05-24T21:51:32Z</dc:date>
    <item>
      <title>CPU Performances issues when running input powershell scripts</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/CPU-Performances-issues-when-running-input-powershell-scripts/m-p/117495#M1390</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I'm using 4 powershell scripts to gather different infos on my machine (Windows server 2012) .&lt;BR /&gt;
 I run the scripts every 5 seconds and i can observe a lot of fluctuations on the CPU Usage who's jumping from 0 to 80% every 5 seconds (script execution).&lt;BR /&gt;
My configuration follows the splunk recommandations and using empty scripts doesn't change anything.&lt;BR /&gt;
Is that normal?&lt;BR /&gt;
Do you have any solutions in order to prevent that?&lt;/P&gt;</description>
      <pubDate>Fri, 22 May 2015 14:39:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/CPU-Performances-issues-when-running-input-powershell-scripts/m-p/117495#M1390</guid>
      <dc:creator>np75014</dc:creator>
      <dc:date>2015-05-22T14:39:28Z</dc:date>
    </item>
    <item>
      <title>Re: CPU Performances issues when running input powershell scripts</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/CPU-Performances-issues-when-running-input-powershell-scripts/m-p/117496#M1391</link>
      <description>&lt;P&gt;Yes, do something else useful on the server.  Why do you care that CPU goes to 80%?  If the server is sitting there totally idle (CPU=0%), then it makes perfect sense for the OS/scheduler to allot what would normally be excessive resources to a low priority task.  I would expect and desire it to do exactly that; why do you expect otherwise?&lt;/P&gt;</description>
      <pubDate>Sun, 24 May 2015 21:51:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/CPU-Performances-issues-when-running-input-powershell-scripts/m-p/117496#M1391</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2015-05-24T21:51:32Z</dc:date>
    </item>
    <item>
      <title>Re: CPU Performances issues when running input powershell scripts</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/CPU-Performances-issues-when-running-input-powershell-scripts/m-p/117497#M1392</link>
      <description>&lt;P&gt;Thanks for your reply.&lt;BR /&gt;
The reason why we don’t want to impact the CPU usage that much is because our solution is supposed to monitor the machine for abnormal usage. We do not want to be disruptive.&lt;BR /&gt;
Running the script outside Splunk does not cause problems.&lt;/P&gt;

&lt;P&gt;Do you have the same behavior, and do you confirm it’s expected behavior?&lt;/P&gt;</description>
      <pubDate>Wed, 27 May 2015 14:00:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/CPU-Performances-issues-when-running-input-powershell-scripts/m-p/117497#M1392</guid>
      <dc:creator>np75014</dc:creator>
      <dc:date>2015-05-27T14:00:59Z</dc:date>
    </item>
  </channel>
</rss>

