<?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 arcgisscripting to arcpy - any speed improvement? in Python Questions</title>
    <link>https://community.esri.com/t5/python-questions/arcgisscripting-to-arcpy-any-speed-improvement/m-p/380007#M29986</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just curious, does converting older scripts from arcgisscripting to arcpy gain any speed improvements?&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Obviously for some things, using the 64bit engine could create some good results but I'm more curious just about the basic 32 bit engines.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 28 Oct 2014 03:38:44 GMT</pubDate>
    <dc:creator>PaulDavidson1</dc:creator>
    <dc:date>2014-10-28T03:38:44Z</dc:date>
    <item>
      <title>arcgisscripting to arcpy - any speed improvement?</title>
      <link>https://community.esri.com/t5/python-questions/arcgisscripting-to-arcpy-any-speed-improvement/m-p/380007#M29986</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just curious, does converting older scripts from arcgisscripting to arcpy gain any speed improvements?&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Obviously for some things, using the 64bit engine could create some good results but I'm more curious just about the basic 32 bit engines.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Oct 2014 03:38:44 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/arcgisscripting-to-arcpy-any-speed-improvement/m-p/380007#M29986</guid>
      <dc:creator>PaulDavidson1</dc:creator>
      <dc:date>2014-10-28T03:38:44Z</dc:date>
    </item>
    <item>
      <title>Re: arcgisscripting to arcpy - any speed improvement?</title>
      <link>https://community.esri.com/t5/python-questions/arcgisscripting-to-arcpy-any-speed-improvement/m-p/380008#M29987</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;the new &lt;A href="http://resources.arcgis.com/en/help/main/10.2/index.html#//002z0000001q000000"&gt;data access cursors&lt;/A&gt; module is faster&lt;/P&gt;&lt;P&gt;You can always explore the &lt;A href="http://resources.arcgis.com/en/help/main/10.2/index.html#/What_s_new_in_ArcGIS_10_2_2/016w0000005w000000/"&gt;What's New section &lt;/A&gt;to see things that are specifically of interest to you&lt;/P&gt;&lt;P&gt;Python and numpy have been updated&lt;BR /&gt;The list of improvements by 10.x version number can be found in the what's new section&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Oct 2014 10:19:13 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/arcgisscripting-to-arcpy-any-speed-improvement/m-p/380008#M29987</guid>
      <dc:creator>DanPatterson_Retired</dc:creator>
      <dc:date>2014-10-28T10:19:13Z</dc:date>
    </item>
    <item>
      <title>Re: arcgisscripting to arcpy - any speed improvement?</title>
      <link>https://community.esri.com/t5/python-questions/arcgisscripting-to-arcpy-any-speed-improvement/m-p/380009#M29988</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;arcpy mostly just wraps arcgisscripting in a Python-programmer-friendly way. Like Dan said, arcpy.da cursors are way faster. Otherwise any speed improvements you'd see in arcpy (I'm not aware of too many, aside from a few specific geoprocessing tools that now benchmark better) will also apply to arcgisscripting.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 Oct 2014 16:40:21 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/arcgisscripting-to-arcpy-any-speed-improvement/m-p/380009#M29988</guid>
      <dc:creator>JasonScheirer</dc:creator>
      <dc:date>2014-10-29T16:40:21Z</dc:date>
    </item>
    <item>
      <title>Re: arcgisscripting to arcpy - any speed improvement?</title>
      <link>https://community.esri.com/t5/python-questions/arcgisscripting-to-arcpy-any-speed-improvement/m-p/380010#M29989</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks guys.&lt;/P&gt;&lt;P&gt;I guess that means that other than using the much easier to use cursors, there's no real point in converting arcgisscripting code, at least from a performance standpoint.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My experience is almost all with arcpy but I guess I should review the what's new to see if there are some issues that might clean up or speed up.&amp;nbsp; Guess I'd just have to do some tests.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'd imagine that for some of our stuff, where we're manipulating large SDE databases and creating file gdbs for websites, that going to 64bit version might speed things up quite a bit.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 Oct 2014 16:52:57 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/arcgisscripting-to-arcpy-any-speed-improvement/m-p/380010#M29989</guid>
      <dc:creator>PaulDavidson1</dc:creator>
      <dc:date>2014-10-29T16:52:57Z</dc:date>
    </item>
  </channel>
</rss>

