<?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>idea Performance of caching workflow in ArcGIS Pro in ArcGIS Enterprise Ideas</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-ideas/performance-of-caching-workflow-in-arcgis-pro/idi-p/923463</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ArcGIS Pro is able to generate 2D cache &amp;nbsp;as a tileCache or by using portal for ArcGIS.&lt;/P&gt;&lt;P&gt;It's no longer possible to publish directly to an ArcGIS Server GIS Server.&lt;/P&gt;&lt;P&gt;As a result, caching workflow is slow (ArcGIS Pro is not scalable as it's documented) and we can't have high performance workflow as we had in the past with direct publish/ShareAs to ArcGIS Server and make GIS Server calculate the cache. It's a real mistake when we have to build huge cache that take many days to process.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please find a way to fix that. If not, customers will have troubles to move forward with ArcGIS Pro and 10.5.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 16 Jan 2017 09:05:26 GMT</pubDate>
    <dc:creator>ThierryBOCH</dc:creator>
    <dc:date>2017-01-16T09:05:26Z</dc:date>
    <item>
      <title>Performance of caching workflow in ArcGIS Pro</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-ideas/performance-of-caching-workflow-in-arcgis-pro/idi-p/923463</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ArcGIS Pro is able to generate 2D cache &amp;nbsp;as a tileCache or by using portal for ArcGIS.&lt;/P&gt;&lt;P&gt;It's no longer possible to publish directly to an ArcGIS Server GIS Server.&lt;/P&gt;&lt;P&gt;As a result, caching workflow is slow (ArcGIS Pro is not scalable as it's documented) and we can't have high performance workflow as we had in the past with direct publish/ShareAs to ArcGIS Server and make GIS Server calculate the cache. It's a real mistake when we have to build huge cache that take many days to process.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please find a way to fix that. If not, customers will have troubles to move forward with ArcGIS Pro and 10.5.&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jan 2017 09:05:26 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-ideas/performance-of-caching-workflow-in-arcgis-pro/idi-p/923463</guid>
      <dc:creator>ThierryBOCH</dc:creator>
      <dc:date>2017-01-16T09:05:26Z</dc:date>
    </item>
  </channel>
</rss>

