<?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: Python processing running twice as slow each run in Python Questions</title>
    <link>https://community.esri.com/t5/python-questions/python-processing-running-twice-as-slow-each-run/m-p/566721#M44373</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I'm using pyscripter. At the end of the processing, I delete individual aspects in the memory as well as the memory as a whole.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 04 Apr 2012 16:56:45 GMT</pubDate>
    <dc:creator>SarahOishi</dc:creator>
    <dc:date>2012-04-04T16:56:45Z</dc:date>
    <item>
      <title>Python processing running twice as slow each run</title>
      <link>https://community.esri.com/t5/python-questions/python-processing-running-twice-as-slow-each-run/m-p/566719#M44371</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I have a script that processes roads in different counties and builds a dictionary of road lengths in polygons. Due to the large size of the datasets I am building the dictionary "in_memory." The first time I ran this, it processed fairly quickly. The second time I ran the same script on the same data and the processing time doubled. I ran it a third time (on different data, with not much difference in dataset size) and the time doubled from the second run. I am deleting the "in_memory" as one of the first steps of my script to ensure a clear workspace. Any ideas on why it is getting slower each run?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Apr 2012 16:44:56 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/python-processing-running-twice-as-slow-each-run/m-p/566719#M44371</guid>
      <dc:creator>SarahOishi</dc:creator>
      <dc:date>2012-04-04T16:44:56Z</dc:date>
    </item>
    <item>
      <title>Re: Python processing running twice as slow each run</title>
      <link>https://community.esri.com/t5/python-questions/python-processing-running-twice-as-slow-each-run/m-p/566720#M44372</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Are you executing this through IDLE? If so, does killing the process solve the issue? Is memory not being release after each run?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Apr 2012 16:49:09 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/python-processing-running-twice-as-slow-each-run/m-p/566720#M44372</guid>
      <dc:creator>MathewCoyle</dc:creator>
      <dc:date>2012-04-04T16:49:09Z</dc:date>
    </item>
    <item>
      <title>Re: Python processing running twice as slow each run</title>
      <link>https://community.esri.com/t5/python-questions/python-processing-running-twice-as-slow-each-run/m-p/566721#M44373</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I'm using pyscripter. At the end of the processing, I delete individual aspects in the memory as well as the memory as a whole.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Apr 2012 16:56:45 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/python-processing-running-twice-as-slow-each-run/m-p/566721#M44373</guid>
      <dc:creator>SarahOishi</dc:creator>
      <dc:date>2012-04-04T16:56:45Z</dc:date>
    </item>
    <item>
      <title>Re: Python processing running twice as slow each run</title>
      <link>https://community.esri.com/t5/python-questions/python-processing-running-twice-as-slow-each-run/m-p/566722#M44374</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Does killing the PyScripter.exe process or rebooting solve the issue?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;And does the memory being held by the process release after you delete your in memory workspace or does it persist?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Apr 2012 17:03:15 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/python-processing-running-twice-as-slow-each-run/m-p/566722#M44374</guid>
      <dc:creator>MathewCoyle</dc:creator>
      <dc:date>2012-04-04T17:03:15Z</dc:date>
    </item>
    <item>
      <title>Re: Python processing running twice as slow each run</title>
      <link>https://community.esri.com/t5/python-questions/python-processing-running-twice-as-slow-each-run/m-p/566723#M44375</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Killing and rebooting does not solve the issue.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I'm not sure if the memory is being released. The in_memory workspace size remains constant throughout processing though (before deleting, after deleting and after building a dictionary).&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Apr 2012 18:58:20 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/python-processing-running-twice-as-slow-each-run/m-p/566723#M44375</guid>
      <dc:creator>SarahOishi</dc:creator>
      <dc:date>2012-04-04T18:58:20Z</dc:date>
    </item>
  </channel>
</rss>

