<?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: Tool Processing times in Spatial Statistics Questions</title>
    <link>https://community.esri.com/t5/spatial-statistics-questions/tool-processing-times/m-p/53660#M180</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Mark,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks for the reply. I have 2,023,089 records in my point shapefile, so I expected a long processing time. It's still running at this moment, though for some reason it went from pulling 1.2GB of ram down to ~68MB.. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It's good to know that the next release will likely be faster. I'm assuming then that at the moment there is no simple way to estimate processing times?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Dan&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 15 Nov 2013 15:53:37 GMT</pubDate>
    <dc:creator>DanielJarvis</dc:creator>
    <dc:date>2013-11-15T15:53:37Z</dc:date>
    <item>
      <title>Tool Processing times</title>
      <link>https://community.esri.com/t5/spatial-statistics-questions/tool-processing-times/m-p/53658#M178</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi all,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I was wondering if anyone knew of a tool or calculator of some sort available to estimate processing times. For instance, I am using the Multi-Distance Spatial Cluster Analysis (Ripleys K Function) tool on a point shapefile that is 121mb and it has been running for a day and a half and is still not completed. I have defined an irregular extent and am using 999 random permutations for confidence intervals. The computer I am using has an i5 processor, is 64bit, and has 6g of RAM, and I am using arc10.2. I would like to be able make estimations of processing times for tools like this. Is that possible?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks for any help you can offer,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Dan&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Nov 2013 16:52:54 GMT</pubDate>
      <guid>https://community.esri.com/t5/spatial-statistics-questions/tool-processing-times/m-p/53658#M178</guid>
      <dc:creator>DanielJarvis</dc:creator>
      <dc:date>2013-11-14T16:52:54Z</dc:date>
    </item>
    <item>
      <title>Re: Tool Processing times</title>
      <link>https://community.esri.com/t5/spatial-statistics-questions/tool-processing-times/m-p/53659#M179</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Dan,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;While k-function has had some speed improvements over the last few releases, it is an inherently slow algorithm.&amp;nbsp; How many point features do you have?&amp;nbsp; The 999 permutations are causing the delay... but it shouldn't run out of memory... so at some point it should finish.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;At 10.2.1 we have moved a portion of our core calculations to C++ to improve performance.&amp;nbsp; k-function is set for this improvement in the next release [i.e. post 10.2.1].&amp;nbsp; We got 50 times the speed for some of our clustering algorithms... so perhaps k-function will see a dramatic improvement as well in the future.&amp;nbsp; That being said, the nature of the algorithm will always be poor from a Big O perspective.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Nov 2013 15:33:43 GMT</pubDate>
      <guid>https://community.esri.com/t5/spatial-statistics-questions/tool-processing-times/m-p/53659#M179</guid>
      <dc:creator>MarkJanikas</dc:creator>
      <dc:date>2013-11-15T15:33:43Z</dc:date>
    </item>
    <item>
      <title>Re: Tool Processing times</title>
      <link>https://community.esri.com/t5/spatial-statistics-questions/tool-processing-times/m-p/53660#M180</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Mark,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks for the reply. I have 2,023,089 records in my point shapefile, so I expected a long processing time. It's still running at this moment, though for some reason it went from pulling 1.2GB of ram down to ~68MB.. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It's good to know that the next release will likely be faster. I'm assuming then that at the moment there is no simple way to estimate processing times?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Dan&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Nov 2013 15:53:37 GMT</pubDate>
      <guid>https://community.esri.com/t5/spatial-statistics-questions/tool-processing-times/m-p/53660#M180</guid>
      <dc:creator>DanielJarvis</dc:creator>
      <dc:date>2013-11-15T15:53:37Z</dc:date>
    </item>
  </channel>
</rss>

