<?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 Does INASolver Solve method supports mutithreading in ArcGIS Network Analyst Questions</title>
    <link>https://community.esri.com/t5/arcgis-network-analyst-questions/does-inasolver-solve-method-supports-mutithreading/m-p/453122#M4307</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I need to know does INASolver Solve method supports multi-threading. &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Because when I implemented in my code to call Solve method in multiple treads for solving more than 1000 locations its taking more time than regular solve using 4-threads. &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Regular solve is taking -&amp;gt;45 mins&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;multithreading using 4 threads consuming --&amp;gt; 52 mins&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It looks to me INASolver--&amp;gt;Solve() method does synchronization of threads (observed by keeping logging.)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Eg: Thread call are like:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Before solve thread 3 called&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Before solve thread 2 called&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Before solve thread 1 called&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Before solve thread 4 called&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;After Solve method:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; After solve thread 4 called&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;After solve thread 1 called&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;After solve thread 2 called&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;After solve thread 3 called&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2014 06:08:30 GMT</pubDate>
    <dc:creator>MuraliChoudari</dc:creator>
    <dc:date>2014-06-05T06:08:30Z</dc:date>
    <item>
      <title>Does INASolver Solve method supports mutithreading</title>
      <link>https://community.esri.com/t5/arcgis-network-analyst-questions/does-inasolver-solve-method-supports-mutithreading/m-p/453122#M4307</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I need to know does INASolver Solve method supports multi-threading. &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Because when I implemented in my code to call Solve method in multiple treads for solving more than 1000 locations its taking more time than regular solve using 4-threads. &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Regular solve is taking -&amp;gt;45 mins&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;multithreading using 4 threads consuming --&amp;gt; 52 mins&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It looks to me INASolver--&amp;gt;Solve() method does synchronization of threads (observed by keeping logging.)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Eg: Thread call are like:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Before solve thread 3 called&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Before solve thread 2 called&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Before solve thread 1 called&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Before solve thread 4 called&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;After Solve method:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; After solve thread 4 called&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;After solve thread 1 called&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;After solve thread 2 called&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;After solve thread 3 called&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2014 06:08:30 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-network-analyst-questions/does-inasolver-solve-method-supports-mutithreading/m-p/453122#M4307</guid>
      <dc:creator>MuraliChoudari</dc:creator>
      <dc:date>2014-06-05T06:08:30Z</dc:date>
    </item>
  </channel>
</rss>

