ArcGIS Pro performance issues

[JimGarcia1]

We occasionally are having issues of ArcGIS Pro. We have certain layers in our enterprise database that take forever to load. Sometimes they load quickly, and editing is quick and easy, and at other times, it can loop forever and ever to load. We re-set the server, but that doesn't seem to do anything. And then the next day, or even a few hours later in the same day, it works again. Also, it seems to be the layers in a specific dataset, so I am assuming something at the Feature Dataset level? 

[CodyPatterson]

Hey @JimGarcia1 

To me, this sounds like an indexing issue, or some type of data bandwidth issue.

I would verify that all layers in the database are properly indexed and are defragmented, a buildup of fragmentation can cause slowness and indexes not being present may cause the queries to take especially long.

Along with that, I would check with your IT dept to see if there is a bandwidth issue on your network, if you're using a VPN then you'll more than likely encounter bandwidth issues.

Finally, if you have access to ArcGIS Monitor or it's installed on your environment, I would check to see if there are any major issues there that you can spot, you may check resource utilization as well as it may be happening during large loads on the server.

Cody

[RTPL_AU]

@JimGarcia1  Which version are you on?

The license checking bug in < 3.5 can cause significant issues in all areas Pro. 
Use Diag Monitor to check before you go on a wild goose chase with IT blaming their network 😀

[CalvinHarmin]

Can you describe that license check bug? I haven’t heard of that one yet.

[SimonSchütte_ct]

ArcGIS Pro will try to verify the license every few seconds. This is resolved in the latest release.

Best analyse what is going on using the Diagnostic Monitor—ArcGIS Pro | Documentation

[Todd_Metzler]

Is "enterprise database" referring to a 3rd party Relational Data Base Management System (RDBMS) configured to host Enterprise GeoData Base(s) (EGDB)? If yes, what flavor (Microsoft SQL server, Oracle, PostgreSQL...).  If yes, how frequent and at what scale are transactions performed and by how many concurrent editors?  If yes, how often are you running DB maintence like analyze, rebuild index, compress?  If yes, how frequently has your RDBMS adminstator scheduled incremental backups and at what scope?  A good indicator of this is the temporal relationship between poor connection performance and the "backend" RDBMS scheduled maintenance tasks.

Or, are you talking about a flavor of ArcGIS datastore?

[Melissa_B]

Are the layers being accessed directly through something like an SDE connection or are they Portal services that you are referencing in the project?  If it's portal services, then it sounds like a cold start issue - depending on how the service is configured, if there's not one constant background instance sitting on the server at all times, then when the service is queried, it has to load up the instance on request which takes a bit.  The shared versus dedicated instance pools and the minimum number of instances have to be tuned to balance memory usage on the server and speed: https://www.esri.com/arcgis-blog/products/arcgis-enterprise/administration/shared-instances-arcgis-s...

It might also be related to database maintenance tasks - rebuilding indexes and analyzing statistics for the database and the datasets within it, reconciling versions, and compressing the database. https://desktop.arcgis.com/en/arcmap/10.5/manage-data/geodatabases/recommended-version-administratio...