<?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 My OpsDash is insanely slow! Any performance tips? in ArcGIS Dashboards Questions</title>
    <link>https://community.esri.com/t5/arcgis-dashboards-questions/my-opsdash-is-insanely-slow-any-performance-tips/m-p/699574#M3711</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Good Morning,&lt;/P&gt;&lt;P&gt;I have created an operations dashboard but it takes FOREVER to load. Aside from any network issues that might be affecting performance, I was wondering if the way I have put the dashboard together may be the culprit. Here are my thoughts and I wanted to put out there for your input/feedback.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The main map that feeds the dashboard is a web map that gets its content from a MapServer REST service&amp;nbsp; ( which connects to a table on a sql server). There are 5 layers in this Map Service. Is keeping these layers in the one Map Service best practice? Or would it be better to have a Map Service for each layer?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When publishing, since I am selecting a registered database as my content source, there is the option to create both a map service and a feature service. Is there any performance benefit for Feature Service over Map Service? And if so, would a feature service with 5 layers suffice? Or should it be a feature service for each layer?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I appreciate any and all feedback. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 22 May 2019 15:14:27 GMT</pubDate>
    <dc:creator>MarkJones7</dc:creator>
    <dc:date>2019-05-22T15:14:27Z</dc:date>
    <item>
      <title>My OpsDash is insanely slow! Any performance tips?</title>
      <link>https://community.esri.com/t5/arcgis-dashboards-questions/my-opsdash-is-insanely-slow-any-performance-tips/m-p/699574#M3711</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Good Morning,&lt;/P&gt;&lt;P&gt;I have created an operations dashboard but it takes FOREVER to load. Aside from any network issues that might be affecting performance, I was wondering if the way I have put the dashboard together may be the culprit. Here are my thoughts and I wanted to put out there for your input/feedback.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The main map that feeds the dashboard is a web map that gets its content from a MapServer REST service&amp;nbsp; ( which connects to a table on a sql server). There are 5 layers in this Map Service. Is keeping these layers in the one Map Service best practice? Or would it be better to have a Map Service for each layer?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When publishing, since I am selecting a registered database as my content source, there is the option to create both a map service and a feature service. Is there any performance benefit for Feature Service over Map Service? And if so, would a feature service with 5 layers suffice? Or should it be a feature service for each layer?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I appreciate any and all feedback. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 May 2019 15:14:27 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-dashboards-questions/my-opsdash-is-insanely-slow-any-performance-tips/m-p/699574#M3711</guid>
      <dc:creator>MarkJones7</dc:creator>
      <dc:date>2019-05-22T15:14:27Z</dc:date>
    </item>
  </channel>
</rss>

