<?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: Predict that the sql text will consume high resources in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Predict-that-the-sql-text-will-consume-high-resources/m-p/452666#M95037</link>
    <description>&lt;P&gt;yes , I am using Splunk MLTK.&lt;BR /&gt;
Is it recommended to do it with Clustering algorithm K-means&lt;/P&gt;</description>
    <pubDate>Mon, 01 Jul 2019 07:15:27 GMT</pubDate>
    <dc:creator>swetar</dc:creator>
    <dc:date>2019-07-01T07:15:27Z</dc:date>
    <item>
      <title>Predict that the sql text will consume high resources</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Predict-that-the-sql-text-will-consume-high-resources/m-p/452664#M95035</link>
      <description>&lt;P&gt;Hi everyone,&lt;BR /&gt;
Req# Predict that the sql text running in the system will consume high resources. &lt;BR /&gt;
I wanted to predict this based on the temp space and undo table space used by the query.&lt;BR /&gt;
I am thinking to use Clustering algo.&lt;BR /&gt;
Can anyone suggest me, which algo should I use. &lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 01 Jul 2019 04:30:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Predict-that-the-sql-text-will-consume-high-resources/m-p/452664#M95035</guid>
      <dc:creator>swetar</dc:creator>
      <dc:date>2019-07-01T04:30:05Z</dc:date>
    </item>
    <item>
      <title>Re: Predict that the sql text will consume high resources</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Predict-that-the-sql-text-will-consume-high-resources/m-p/452665#M95036</link>
      <description>&lt;P&gt;Are you using MLTK ?&lt;/P&gt;</description>
      <pubDate>Mon, 01 Jul 2019 06:59:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Predict-that-the-sql-text-will-consume-high-resources/m-p/452665#M95036</guid>
      <dc:creator>DavidHourani</dc:creator>
      <dc:date>2019-07-01T06:59:02Z</dc:date>
    </item>
    <item>
      <title>Re: Predict that the sql text will consume high resources</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Predict-that-the-sql-text-will-consume-high-resources/m-p/452666#M95037</link>
      <description>&lt;P&gt;yes , I am using Splunk MLTK.&lt;BR /&gt;
Is it recommended to do it with Clustering algorithm K-means&lt;/P&gt;</description>
      <pubDate>Mon, 01 Jul 2019 07:15:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Predict-that-the-sql-text-will-consume-high-resources/m-p/452666#M95037</guid>
      <dc:creator>swetar</dc:creator>
      <dc:date>2019-07-01T07:15:27Z</dc:date>
    </item>
    <item>
      <title>Re: Predict that the sql text will consume high resources</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Predict-that-the-sql-text-will-consume-high-resources/m-p/452667#M95038</link>
      <description>&lt;P&gt;yeah that makes sense if you have multiple queries and you wish to classify them, is that what you're trying to achieve ? &lt;/P&gt;</description>
      <pubDate>Mon, 01 Jul 2019 07:22:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Predict-that-the-sql-text-will-consume-high-resources/m-p/452667#M95038</guid>
      <dc:creator>DavidHourani</dc:creator>
      <dc:date>2019-07-01T07:22:09Z</dc:date>
    </item>
    <item>
      <title>Re: Predict that the sql text will consume high resources</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Predict-that-the-sql-text-will-consume-high-resources/m-p/452668#M95039</link>
      <description>&lt;P&gt;Yes there will be multiple queries. I wanted to classify bad sql ( bad sql meaning, sql which are going to consume more than  80% temp or consuming high io)&lt;/P&gt;</description>
      <pubDate>Mon, 01 Jul 2019 07:37:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Predict-that-the-sql-text-will-consume-high-resources/m-p/452668#M95039</guid>
      <dc:creator>swetar</dc:creator>
      <dc:date>2019-07-01T07:37:40Z</dc:date>
    </item>
    <item>
      <title>Re: Predict that the sql text will consume high resources</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Predict-that-the-sql-text-will-consume-high-resources/m-p/452669#M95040</link>
      <description>&lt;P&gt;In that case try &lt;STRONG&gt;BDSCAN&lt;/STRONG&gt; could be better than fitting into a set number of clusters.&lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/MLApp/4.3.0/User/Algorithms#DBSCAN"&gt;https://docs.splunk.com/Documentation/MLApp/4.3.0/User/Algorithms#DBSCAN&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 01 Jul 2019 07:49:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Predict-that-the-sql-text-will-consume-high-resources/m-p/452669#M95040</guid>
      <dc:creator>DavidHourani</dc:creator>
      <dc:date>2019-07-01T07:49:52Z</dc:date>
    </item>
  </channel>
</rss>

