<?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 'Nice' a scripted input in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Nice-a-scripted-input/m-p/22559#M3493</link>
    <description>&lt;P&gt;Hi all,&lt;/P&gt;

&lt;P&gt;Is there a way to "nice" a scripted input process so that it doesn't swamp the CPU?  I have a scripted input on a LWF that is fairly CPU intensive if you just let it run.  I'd like to "nice" it down to a level where it doesn't swamp the CPU.  &lt;/P&gt;

&lt;P&gt;The script doesn't need to run in a certain amount of time, so just nicing it down should be ok.  I'm open to other approaches as well if people have solved this a different way.  It would also be good to know how to do this on a Windows machine as well.&lt;/P&gt;

&lt;P&gt;Thanks,
Curt&lt;/P&gt;</description>
    <pubDate>Sat, 08 Jan 2011 00:13:24 GMT</pubDate>
    <dc:creator>Curt_Collins</dc:creator>
    <dc:date>2011-01-08T00:13:24Z</dc:date>
    <item>
      <title>'Nice' a scripted input</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Nice-a-scripted-input/m-p/22559#M3493</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;

&lt;P&gt;Is there a way to "nice" a scripted input process so that it doesn't swamp the CPU?  I have a scripted input on a LWF that is fairly CPU intensive if you just let it run.  I'd like to "nice" it down to a level where it doesn't swamp the CPU.  &lt;/P&gt;

&lt;P&gt;The script doesn't need to run in a certain amount of time, so just nicing it down should be ok.  I'm open to other approaches as well if people have solved this a different way.  It would also be good to know how to do this on a Windows machine as well.&lt;/P&gt;

&lt;P&gt;Thanks,
Curt&lt;/P&gt;</description>
      <pubDate>Sat, 08 Jan 2011 00:13:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Nice-a-scripted-input/m-p/22559#M3493</guid>
      <dc:creator>Curt_Collins</dc:creator>
      <dc:date>2011-01-08T00:13:24Z</dc:date>
    </item>
    <item>
      <title>Re: 'Nice' a scripted input</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Nice-a-scripted-input/m-p/22560#M3494</link>
      <description>&lt;P&gt;I would highly recommend throttling utilization within your script rather than relying on NICE, both for portability and for performance reasons.  In other words, if your scripted input is causing a resource problem on your machine, then you are just band-aiding the process by using NICE.&lt;/P&gt;</description>
      <pubDate>Sat, 08 Jan 2011 03:59:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Nice-a-scripted-input/m-p/22560#M3494</guid>
      <dc:creator>araitz</dc:creator>
      <dc:date>2011-01-08T03:59:02Z</dc:date>
    </item>
    <item>
      <title>Re: 'Nice' a scripted input</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Nice-a-scripted-input/m-p/22561#M3495</link>
      <description>&lt;P&gt;You could simply wrap your program inside a shell script that calls your program with "nice", and call that one as your scripted input instead:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;#/bin/sh

nice -10 myprogram
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 10 Jan 2011 06:48:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Nice-a-scripted-input/m-p/22561#M3495</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2011-01-10T06:48:53Z</dc:date>
    </item>
  </channel>
</rss>

