<?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: Performance Metrics for Services in ArcGIS Enterprise Questions</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-questions/performance-metrics-for-services/m-p/1094894#M31042</link>
    <description>Hi,&lt;BR /&gt;This is not what you asked for but it may be helpful. I cannot help you identify the timings for ArcGIS Server response vs database server response but here are a few things that we do to help improve performance on map service requests:&lt;BR /&gt;&lt;BR /&gt;1. Review the web logs on the web adaptors to identify the top 20 slowest map service requests. Our map services are open to the Public so we are susceptible to poorly designed queries. Looking at the slowest map service requests we were recently able to help two municipalities reconfigure their WAB search widget for much faster performance.&lt;BR /&gt;2. When configuring a WAB search widget do not use the "LIKE" operator in the query unless it is absolutely necessary. Using "LIKE" negates any indexing on your tables. Use the "=" operator and your queries will be much faster.&lt;BR /&gt;I hope this helps.&lt;BR /&gt;Bernie.&lt;BR /&gt;</description>
    <pubDate>Thu, 02 Sep 2021 13:44:41 GMT</pubDate>
    <dc:creator>berniejconnors</dc:creator>
    <dc:date>2021-09-02T13:44:41Z</dc:date>
    <item>
      <title>Performance Metrics for Services</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/performance-metrics-for-services/m-p/1094862#M31039</link>
      <description>&lt;P&gt;Hi There, I am looking for a way to generate some metrics around time taken by a map service query at ArcGIS Enterprise 10.6.1.&lt;/P&gt;&lt;P&gt;The chrome log tells me time taken but I want to know if there is a way to breakdown which part of query (GIS Server, database) is taking the longest and way to optimize it.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&amp;nbsp; &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Sep 2021 12:31:19 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/performance-metrics-for-services/m-p/1094862#M31039</guid>
      <dc:creator>Sunnywaygis</dc:creator>
      <dc:date>2021-09-02T12:31:19Z</dc:date>
    </item>
    <item>
      <title>Re: Performance Metrics for Services</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/performance-metrics-for-services/m-p/1094869#M31040</link>
      <description>Hi &lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/469120"&gt;@Sunnywaygis&lt;/a&gt;&lt;BR /&gt;So usually, we would work from the base up if your service was created with a .mxd then you can have a look at mxdperfstat it generates metrics on query and drawing time and will indicate where the service is struggling.&lt;BR /&gt;mxdperfstat - (arcgis.com)&lt;BR /&gt;The Next step after this is to setup monitoring on ArcGIS Server&lt;BR /&gt;The url is &lt;A href="https://your.dns.com:6443/arcgis/manager" target="_blank"&gt;https://your.dns.com:6443/arcgis/manager&lt;/A&gt; or &lt;A href="https://your.dns.com/webadaptor/manager" target="_blank"&gt;https://your.dns.com/webadaptor/manager&lt;/A&gt;&lt;BR /&gt;In server Manager you go to Logs then statistics and create a New Report&lt;BR /&gt;Here you have the option to see Total Requests, Avr. Response Time, Timeouts and Maximum Running Instances&lt;BR /&gt;Hope it helps&lt;BR /&gt;</description>
      <pubDate>Thu, 02 Sep 2021 12:55:41 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/performance-metrics-for-services/m-p/1094869#M31040</guid>
      <dc:creator>HenryLindemann</dc:creator>
      <dc:date>2021-09-02T12:55:41Z</dc:date>
    </item>
    <item>
      <title>Re: Performance Metrics for Services</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/performance-metrics-for-services/m-p/1094881#M31041</link>
      <description>&lt;P&gt;Thanks, will try these options.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Sep 2021 13:18:49 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/performance-metrics-for-services/m-p/1094881#M31041</guid>
      <dc:creator>Sunnywaygis</dc:creator>
      <dc:date>2021-09-02T13:18:49Z</dc:date>
    </item>
    <item>
      <title>Re: Performance Metrics for Services</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/performance-metrics-for-services/m-p/1094894#M31042</link>
      <description>Hi,&lt;BR /&gt;This is not what you asked for but it may be helpful. I cannot help you identify the timings for ArcGIS Server response vs database server response but here are a few things that we do to help improve performance on map service requests:&lt;BR /&gt;&lt;BR /&gt;1. Review the web logs on the web adaptors to identify the top 20 slowest map service requests. Our map services are open to the Public so we are susceptible to poorly designed queries. Looking at the slowest map service requests we were recently able to help two municipalities reconfigure their WAB search widget for much faster performance.&lt;BR /&gt;2. When configuring a WAB search widget do not use the "LIKE" operator in the query unless it is absolutely necessary. Using "LIKE" negates any indexing on your tables. Use the "=" operator and your queries will be much faster.&lt;BR /&gt;I hope this helps.&lt;BR /&gt;Bernie.&lt;BR /&gt;</description>
      <pubDate>Thu, 02 Sep 2021 13:44:41 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/performance-metrics-for-services/m-p/1094894#M31042</guid>
      <dc:creator>berniejconnors</dc:creator>
      <dc:date>2021-09-02T13:44:41Z</dc:date>
    </item>
  </channel>
</rss>

