<?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>idea ArcPy in Script Memory Flush in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/arcpy-in-script-memory-flush/idi-p/929373</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;It would be great to be able to flush my RAM&amp;nbsp;in the midst of a script to prevent my process from being prematurely cancelled out due to a lack of RAM. &amp;nbsp;I&amp;nbsp;am dealing with a number of cursors and files of rows over 1 million. &amp;nbsp;Any ability to clear out the RAM&amp;nbsp;during the operation would be greatly appreciated.&lt;BR /&gt;&lt;BR /&gt;

&lt;!-- content transformation source ID: 08730000000brot --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 28 Sep 2011 17:06:26 GMT</pubDate>
    <dc:creator>MichaelAlires</dc:creator>
    <dc:date>2011-09-28T17:06:26Z</dc:date>
    <item>
      <title>ArcPy in Script Memory Flush</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/arcpy-in-script-memory-flush/idi-p/929373</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;It would be great to be able to flush my RAM&amp;nbsp;in the midst of a script to prevent my process from being prematurely cancelled out due to a lack of RAM. &amp;nbsp;I&amp;nbsp;am dealing with a number of cursors and files of rows over 1 million. &amp;nbsp;Any ability to clear out the RAM&amp;nbsp;during the operation would be greatly appreciated.&lt;BR /&gt;&lt;BR /&gt;

&lt;!-- content transformation source ID: 08730000000brot --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Sep 2011 17:06:26 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/arcpy-in-script-memory-flush/idi-p/929373</guid>
      <dc:creator>MichaelAlires</dc:creator>
      <dc:date>2011-09-28T17:06:26Z</dc:date>
    </item>
    <item>
      <title>Re: ArcPy in Script Memory Flush</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/arcpy-in-script-memory-flush/idc-p/929374#M2440</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;That is a big issue with arcpy. You can manually manage python memory use with garbage collection but the geoprocessor has separate memory space than python so you cant actually do anything to that object.

&lt;!-- content transformation source ID: 00a3000000Bgma0 --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Sep 2011 20:33:23 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/arcpy-in-script-memory-flush/idc-p/929374#M2440</guid>
      <dc:creator>ChrisMathers</dc:creator>
      <dc:date>2011-09-29T20:33:23Z</dc:date>
    </item>
    <item>
      <title>Re: ArcPy in Script Memory Flush</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/arcpy-in-script-memory-flush/idc-p/929375#M2441</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;An effective memory management for ArcPy would be desirable. I am executing lots of tools each one taking the input from its predecessor. Memory usage is ever increasing - seems the occupied resources from each tool are not freed until the whole script has finished.&lt;BR /&gt;

&lt;!-- content transformation source ID: 00a3000000C8nQy --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Oct 2011 09:38:51 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/arcpy-in-script-memory-flush/idc-p/929375#M2441</guid>
      <dc:creator>MatthiasMueller</dc:creator>
      <dc:date>2011-10-26T09:38:51Z</dc:date>
    </item>
    <item>
      <title>Re: ArcPy in Script Memory Flush</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/arcpy-in-script-memory-flush/idc-p/929376#M2442</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It would be great if there was some method on arcpy that&amp;nbsp;purged the memory even if it&amp;nbsp;had a performance hit. If I'm doing large data crunching I'm not going to worry over a few seconds if the data crunching takes several hours.&amp;nbsp; I was imagining something like:&lt;BR /&gt;&lt;BR /&gt;arcpy.ClearMemory&lt;BR /&gt;&lt;BR /&gt;Then behind the scenes this would release cursors and objects that are out of scope etc.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Nov 2011 11:56:31 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/arcpy-in-script-memory-flush/idc-p/929376#M2442</guid>
      <dc:creator>DuncanHornby</dc:creator>
      <dc:date>2011-11-17T11:56:31Z</dc:date>
    </item>
    <item>
      <title>Re: ArcPy in Script Memory Flush</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/arcpy-in-script-memory-flush/idc-p/929377#M2443</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is definitely an area of concern for my operation.&amp;nbsp; We are running about 30 automated&amp;nbsp;geprocessing scripts at night.&amp;nbsp;&lt;/P&gt;

&lt;!-- content transformation source ID: 00a3000000Dc0Vu --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Jan 2012 19:12:48 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/arcpy-in-script-memory-flush/idc-p/929377#M2443</guid>
      <dc:creator>KristinGoff</dc:creator>
      <dc:date>2012-01-25T19:12:48Z</dc:date>
    </item>
    <item>
      <title>Re: ArcPy in Script Memory Flush</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/arcpy-in-script-memory-flush/idc-p/929378#M2444</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;there need to be more options for tackling heavy geoprocessing than the Dice tool, and a memory flush would help greatly.

&lt;!-- content transformation source ID: 00aE00000027YEU --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Jan 2013 17:51:04 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/arcpy-in-script-memory-flush/idc-p/929378#M2444</guid>
      <dc:creator>JamieKass</dc:creator>
      <dc:date>2013-01-10T17:51:04Z</dc:date>
    </item>
    <item>
      <title>Re: ArcPy in Script Memory Flush</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/arcpy-in-script-memory-flush/idc-p/929379#M2445</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;I agree with the previous comments.&lt;BR /&gt;My concern is also the crunching of a large database (over 4gb and millions of entries).&lt;BR /&gt;After the database, which i want to prozess, reaches a certain size arcpy gives me some error.&lt;BR /&gt;When i check my RAM load everything is clear. Even when i use something like "arcpy.Delete_management" there is no reduction in memory load.&lt;BR /&gt;Please optimize this. Currently arcpy is unusable in the way i like.

&lt;!-- content transformation source ID: 00aE00000028qju --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 03 Mar 2013 15:29:36 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/arcpy-in-script-memory-flush/idc-p/929379#M2445</guid>
      <dc:creator>MatthiasGlosa</dc:creator>
      <dc:date>2013-03-03T15:29:36Z</dc:date>
    </item>
    <item>
      <title>Re: ArcPy in Script Memory Flush</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/arcpy-in-script-memory-flush/idc-p/929380#M2446</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Maybe that is why using spatialite on large datasets works so much better.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Jul 2019 03:51:21 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/arcpy-in-script-memory-flush/idc-p/929380#M2446</guid>
      <dc:creator>KimOllivier</dc:creator>
      <dc:date>2019-07-01T03:51:21Z</dc:date>
    </item>
  </channel>
</rss>

