<?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 Re: Big difference between REST and Geoprocessor query performance in ArcGIS Enterprise Questions</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-questions/big-difference-between-rest-and-geoprocessor-query/m-p/169609#M6745</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;it is not exactly the same thing: &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;1) One drawback of geoprocessing services is that they have a relatively large memory footprint and may run slower.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2) Select by attributes stores the selection so if you have many rows in result of query, the result is stored in a table&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 19 Jun 2014 10:20:39 GMT</pubDate>
    <dc:creator>nicogis</dc:creator>
    <dc:date>2014-06-19T10:20:39Z</dc:date>
    <item>
      <title>Big difference between REST and Geoprocessor query performance</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/big-difference-between-rest-and-geoprocessor-query/m-p/169608#M6744</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I've written an application for bench marking and tracking performance of ArcGIS Server. As part of the app it does a Javascript API Query Task of a feature layer though the REST and later runs the Select By Attribute GP tool from a Geoprocessing Task. This is the same SDE feature class with about 1.34 million polygons, it has both spatial and attribute indexes in place. The query runs in about 1 second from the REST but takes 1 1/2 minutes from the GP Tool. What is up with that?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The SDE feature class is in PostgreSQL SDE 10.2.2&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ArcGIS Server 10.2.2&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Windows 2008 r2&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The definition query and rendering performance is great! GP is really slow!&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Dave&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Jun 2014 18:36:40 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/big-difference-between-rest-and-geoprocessor-query/m-p/169608#M6744</guid>
      <dc:creator>DaveHighness</dc:creator>
      <dc:date>2014-06-17T18:36:40Z</dc:date>
    </item>
    <item>
      <title>Re: Big difference between REST and Geoprocessor query performance</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/big-difference-between-rest-and-geoprocessor-query/m-p/169609#M6745</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;it is not exactly the same thing: &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;1) One drawback of geoprocessing services is that they have a relatively large memory footprint and may run slower.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;2) Select by attributes stores the selection so if you have many rows in result of query, the result is stored in a table&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Jun 2014 10:20:39 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/big-difference-between-rest-and-geoprocessor-query/m-p/169609#M6745</guid>
      <dc:creator>nicogis</dc:creator>
      <dc:date>2014-06-19T10:20:39Z</dc:date>
    </item>
  </channel>
</rss>

