<?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 Parallel processing of batched geoprocessing tasks in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/parallel-processing-of-batched-geoprocessing-tasks/idi-p/972929</link>
    <description>&lt;P&gt;It's well known that ArcGIS only takes advantage of multiple processing threads to allow a &lt;STRONG&gt;single&lt;/STRONG&gt; geoprossesing task to occur in the background while still interacting with the GUI. Any further processing is placed in a queue. A signifficant improvement on this (other than making the whole program multi-thread capable) would be to make batch geoprocessing tasks utilise more than the single thread currently used. If I run a batch of 4 Clip processes, there's probably no reason that at least two can't be run on parallel threads on a modern workstation (even my 3 year old workstation has 4 cores).&lt;BR /&gt;&lt;BR /&gt;This could also provide some relief for the fact that ArcGIS for Desktop is 32-Bit and hence somewhat hamstrung by limited memory access - processing large datasets which run out of memory could be done by breaking them down into tiles and running the required geoprocess on the tiles in parallel.&lt;/P&gt;&lt;!--  content transformation source ID: 087E00000004PCz  --&gt;</description>
    <pubDate>Fri, 11 Aug 2023 21:58:19 GMT</pubDate>
    <dc:creator>AdamForknall</dc:creator>
    <dc:date>2023-08-11T21:58:19Z</dc:date>
    <item>
      <title>Parallel processing of batched geoprocessing tasks</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/parallel-processing-of-batched-geoprocessing-tasks/idi-p/972929</link>
      <description>&lt;P&gt;It's well known that ArcGIS only takes advantage of multiple processing threads to allow a &lt;STRONG&gt;single&lt;/STRONG&gt; geoprossesing task to occur in the background while still interacting with the GUI. Any further processing is placed in a queue. A signifficant improvement on this (other than making the whole program multi-thread capable) would be to make batch geoprocessing tasks utilise more than the single thread currently used. If I run a batch of 4 Clip processes, there's probably no reason that at least two can't be run on parallel threads on a modern workstation (even my 3 year old workstation has 4 cores).&lt;BR /&gt;&lt;BR /&gt;This could also provide some relief for the fact that ArcGIS for Desktop is 32-Bit and hence somewhat hamstrung by limited memory access - processing large datasets which run out of memory could be done by breaking them down into tiles and running the required geoprocess on the tiles in parallel.&lt;/P&gt;&lt;!--  content transformation source ID: 087E00000004PCz  --&gt;</description>
      <pubDate>Fri, 11 Aug 2023 21:58:19 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/parallel-processing-of-batched-geoprocessing-tasks/idi-p/972929</guid>
      <dc:creator>AdamForknall</dc:creator>
      <dc:date>2023-08-11T21:58:19Z</dc:date>
    </item>
    <item>
      <title>Re: Parallel processing of batched geoprocessing tasks</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/parallel-processing-of-batched-geoprocessing-tasks/idc-p/972930#M9644</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;It would be really nice if geoprocessing tasks were thread assignable.

&lt;!-- content transformation source ID: 00aE0000000WVK0 --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 06 Oct 2012 02:30:58 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/parallel-processing-of-batched-geoprocessing-tasks/idc-p/972930#M9644</guid>
      <dc:creator>AaronAddison</dc:creator>
      <dc:date>2012-10-06T02:30:58Z</dc:date>
    </item>
    <item>
      <title>Re: Parallel processing of batched geoprocessing tasks</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/parallel-processing-of-batched-geoprocessing-tasks/idc-p/972931#M9645</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;SP1 for ArcGIS 10.1 Desktop will add paralelel processing. Stay tuned.

&lt;!-- content transformation source ID: 00aE0000000Wv9a --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Oct 2012 13:27:56 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/parallel-processing-of-batched-geoprocessing-tasks/idc-p/972931#M9645</guid>
      <dc:creator>VytautasGipiskis</dc:creator>
      <dc:date>2012-10-30T13:27:56Z</dc:date>
    </item>
    <item>
      <title>Re: Parallel processing of batched geoprocessing tasks</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/parallel-processing-of-batched-geoprocessing-tasks/idc-p/972932#M9646</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;don't hold your breath vgipiskis

&lt;!-- content transformation source ID: 00aE0000000WzQI --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Nov 2012 05:33:13 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/parallel-processing-of-batched-geoprocessing-tasks/idc-p/972932#M9646</guid>
      <dc:creator>AdamForknall</dc:creator>
      <dc:date>2012-11-02T05:33:13Z</dc:date>
    </item>
    <item>
      <title>Re: Parallel processing of batched geoprocessing tasks</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/parallel-processing-of-batched-geoprocessing-tasks/idc-p/972933#M9647</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Background geoprocessing at 10.1 accomodates 64-bit architecture, and you're limited to (IIRC) 60% of your total system memory rather than 2 GB. It's still possible to run out of memory (as I just did a moment ago with a Model) but it's a marked improvement over foreground geoprocessing.

&lt;!-- content transformation source ID: 00aE00000030mTH --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Jul 2013 23:30:56 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/parallel-processing-of-batched-geoprocessing-tasks/idc-p/972933#M9647</guid>
      <dc:creator>JoeChampagne</dc:creator>
      <dc:date>2013-07-31T23:30:56Z</dc:date>
    </item>
    <item>
      <title>Re: Parallel processing of batched geoprocessing tasks</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/parallel-processing-of-batched-geoprocessing-tasks/idc-p/972934#M9648</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;indeed it does&amp;nbsp;&lt;A class="ibtUserLinkNormal ibtUserLink" href="https://c.na9.visual.force.com/apex/ideaProfileActivity?c=09a300000004xET&amp;amp;u=005E0000001mYnyIAE" style="color: rgb(44, 113, 4); font-size: 11px; background-color: rgb(242, 246, 235); text-decoration: none; font-family: verdana;" target="_blank"&gt;jchampagne2&amp;nbsp;&lt;/A&gt;, however it does not accommodate parallel processing, which is the who point of this idea :-)

&lt;!-- content transformation source ID: 00aE00000031FA8 --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Aug 2013 19:34:06 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/parallel-processing-of-batched-geoprocessing-tasks/idc-p/972934#M9648</guid>
      <dc:creator>AdamForknall</dc:creator>
      <dc:date>2013-08-16T19:34:06Z</dc:date>
    </item>
  </channel>
</rss>

