<?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 YAOMI WECFS: Yet Another Out of Memory Issue While Executing Closest Facility Solver in ArcGIS Network Analyst Questions</title>
    <link>https://community.esri.com/t5/arcgis-network-analyst-questions/yaomi-wecfs-yet-another-out-of-memory-issue-while/m-p/361801#M3387</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm facing an Out of Memory issue with pretty massive 'Closest Facility' calculations: 34,000+ incidents (major roads' centroids) x 79 destinations (firestations).&lt;/P&gt;&lt;P&gt;The Python script execution failed after 37 minutes: the log file indicated that destinations and incidents feature classes had been loaded into memory and that the solver had begun calculations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Settings:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;16 Gb RAM&lt;/LI&gt;&lt;LI&gt;Windows 8 Enterprise (64 bits)&lt;/LI&gt;&lt;LI&gt;Intel Core Quad CPU Q9650 3.00 GHz&lt;/LI&gt;&lt;LI&gt;ArcGIS for Desktop 10.2.2.3552 - Advanced licence&lt;/LI&gt;&lt;LI&gt;Network Analyst for ArcGIS 10.2.2&lt;/LI&gt;&lt;LI&gt;Inhouse Road Network (100,000+ segments - 4,500 sq km)&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've read a couple of similar posts on GeoNet blog but pretty much all are from 2011 and the "chunking" method is outdated since ArcGIS 10.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'll be glad to read any feedback on similar issues and get some hints on how to overcome them. All the more than I'll have to compute on a 3-time more massive dataset!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks a lot in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Yann&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PS: I used to perform this kind of calculations with Avenue scripts on ArcView GIS 3.2 with Network Analyst 1.0... It usually took 12 hours to run &lt;SPAN style="text-decoration: underline;"&gt;successfully.&lt;/SPAN&gt; Hope I won't have to migrate back from Python to Avenue, from 10.2 to 3.2! &lt;IMG src="https://community.esri.com/legacyfs/online/emoticons/wink.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 01 Oct 2015 13:49:58 GMT</pubDate>
    <dc:creator>YannKACENELEN</dc:creator>
    <dc:date>2015-10-01T13:49:58Z</dc:date>
    <item>
      <title>YAOMI WECFS: Yet Another Out of Memory Issue While Executing Closest Facility Solver</title>
      <link>https://community.esri.com/t5/arcgis-network-analyst-questions/yaomi-wecfs-yet-another-out-of-memory-issue-while/m-p/361801#M3387</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm facing an Out of Memory issue with pretty massive 'Closest Facility' calculations: 34,000+ incidents (major roads' centroids) x 79 destinations (firestations).&lt;/P&gt;&lt;P&gt;The Python script execution failed after 37 minutes: the log file indicated that destinations and incidents feature classes had been loaded into memory and that the solver had begun calculations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Settings:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;16 Gb RAM&lt;/LI&gt;&lt;LI&gt;Windows 8 Enterprise (64 bits)&lt;/LI&gt;&lt;LI&gt;Intel Core Quad CPU Q9650 3.00 GHz&lt;/LI&gt;&lt;LI&gt;ArcGIS for Desktop 10.2.2.3552 - Advanced licence&lt;/LI&gt;&lt;LI&gt;Network Analyst for ArcGIS 10.2.2&lt;/LI&gt;&lt;LI&gt;Inhouse Road Network (100,000+ segments - 4,500 sq km)&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've read a couple of similar posts on GeoNet blog but pretty much all are from 2011 and the "chunking" method is outdated since ArcGIS 10.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'll be glad to read any feedback on similar issues and get some hints on how to overcome them. All the more than I'll have to compute on a 3-time more massive dataset!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks a lot in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Yann&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PS: I used to perform this kind of calculations with Avenue scripts on ArcView GIS 3.2 with Network Analyst 1.0... It usually took 12 hours to run &lt;SPAN style="text-decoration: underline;"&gt;successfully.&lt;/SPAN&gt; Hope I won't have to migrate back from Python to Avenue, from 10.2 to 3.2! &lt;IMG src="https://community.esri.com/legacyfs/online/emoticons/wink.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Oct 2015 13:49:58 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-network-analyst-questions/yaomi-wecfs-yet-another-out-of-memory-issue-while/m-p/361801#M3387</guid>
      <dc:creator>YannKACENELEN</dc:creator>
      <dc:date>2015-10-01T13:49:58Z</dc:date>
    </item>
  </channel>
</rss>

