Arcpro soooo slow my grandmother out performs it

[BrendanCarroll]

it's unusable most times. not just rendering maps but gp ops are total dead dogs

[DanPatterson_Retired]

speaking of slow... https://community.esri.com/search.jspa?q=slow 

reported in many forms with suggestions and where things might bottle neck.. started 2 years ago and a real favorite

https://community.esri.com/message/705018-why-does-arcgis-pro-have-to-be-so-slow 

[BrendanCarroll]

Yeah I've seen and read a bunch of those threads. So i gotta ask, when does performance become the priority and goofy little bells and whistles get put on hold?

[EricAnderson17]

Hi Brendan,

Can you share any specifics about the workflows or tools you use in ArcGIS Pro where you notice its slow?

Where is your data stored? Locally? On a network drive? 

Have you checked the System Requirements page to make sure your machine is optimal? 

Best regards,

Eric

[KoryKramer]

Looks like some of the details are over on: https://community.esri.com/people/dylanh0/blog/2019/04/10/basic-geoprocessing-in-pro-is-slow?comment...

I'm running 3.2 with Enterprise 10.7 against Azure PostgresSQL 10 on the default 4 core instance. I have all the latest 10.7 Enterprise service packs as of this writing and the performance of all GP functions is unbearable. Copy paste of simple filegb model to Azure - 20Mins. Register as versioned - 5 mins. etc...

I'm assuming Pro 2.3.

Brendan Carroll‌ if you're working with local data what does performance look like?  I'm wondering how much could be related to network latency.  Do you have any benchmark data using other applications that are hitting the database in Azure?

[George_Thompson]

To add to what Kory mentions I found this in the help:

• ArcGIS connections to Microsoft Azure must originate from machines within Microsoft Azure. For best performance, connections should originate from machines within the same Azure region.

https://pro.arcgis.com/en/pro-app/help/data/databases/database-requirements-azure-sql-database.htm

Having the ArcGIS Pro client in the cloud with the Azure DB is CRITICAL for performance.

This requirement has been around since ArcMap 10.3.x.

[BrendanCarroll]

Yes the ArcPro box is on the same VNET as the Azure hosted PostgresSQL DB. All of the below are in compliance.

• Microsoft Azure Database for PostgreSQL—Versions 9.5.7, 9.6.2, and 10.3 
• ArcGIS connections to Microsoft Azure must originate from machines within Microsoft Azure. For best performance, connections should originate from machines within the same Azure region.
• Microsoft Azure Database for PostgreSQL is not supported in the Microsoft Azure Government cloud environment.

Azure VM:

• Windows (Windows Server 2019 Datacenter)
• Standard B8ms (8 vcpus, 32 GB memory)
• East US 2

DB:

• PostgresSQL Version 10
• East US 2

I'm running 3.2 with Enterprise 10.7 against Azure PostgresSQL 10 on the default 4 core instance. I have all the latest 10.7 Enterprise service packs as of this writing and the performance of all GP functions is unbearable. Copy paste of simple filegb model to Azure - 20Mins. Register as versioned - 5 mins. etc...

[George_Thompson]

I would recommend opening a Esri Technical Support case to have them investigate.

[BrendanCarroll]

Just to be clear this is an Azure PaaS PostgresSQL offering