ArcGIS Pro 3.3 performance

[HollyTorpey_LSA]

Is anyone else noticing any performance issues in Pro 3.3? We are, but I'm trying to figure out if it's a Pro update issue or something in our network/system configuration (or a combination of the two). Would especially love to hear from others who have updated to Pro 3.3 on a multi-session virtual desktop where users use Pro to work with data stored on cloud-based fileshares.

Thanks in advance! 

[ThomasKäldström]

I still feel it's too slow (Arc GIS Pro 3.3)  but a little bit better after I set projects->opions->display values to:

rendering quality = low
anitaliasing mode = none
Cleare cache on exit = checked
Rendering Engine I use Open GL but not sure if that is the right option

[ThomasMelton_ARDOT]

It seems 3.4.3 is at least workable for us. The performance still isn't up to what 3.0.6 was, but at least we can do our jobs now. Font rendering is still sluggish, but survivable. I have noted a couple of things that causes 3.4.3 to stumble and spin for a bit especially upon opening a aprx:
1) if there is a broken data connection to one or some of the layers or if the network connection to the data sources is up and down.
2) if there is a broken query for any classes of a layer under labeling properties.

I hope that helps someone else out there.

- Thomas

[MatthiasKl]

We also noticed performance issues with ArcGIS Pro Versions >= 3.3. I tested a fresh computer-wide 3.5.2 installation. Adding a new map without a background map sometimes takes over 3 minutes! This is unacceptable. Just like @ThomasMelton_ARDOT , I also observed a lot of Aux CIM worker threads in the Diagnostic Log where giving a CSharedQueue stall timeouts. At first I suspected OneDrive, but the problem cannot always be reproduced.

[Aaron]

CSharedQueue Stall... the new PC LOAD LETTER. Any updates?

[JamesTurner2]

Also looking for an update, we just moved to pro3.3 on Azure and have been having performance issues. This seems to appear a lot in the log.

[waterschapVallei_en_Veluwe]

We have also Pro 3.5.2 and exactly the same messages in  the logging:  CSharedQueue stall timeouts . There is a hang situation after several open Attribute Table's of feature classes in an Enterprise Geodatabase (ArcSDE 11.3) . The timeouts keep going. It seems an inifinite loop. Do you still have these problems? Is there any solution? It seems to me a bug.

[JamesTurner2]

Unfortunately I have no updates for you. I still experience this daily, but we have so many issues with our implementation, it's hard to point a finger at any one thing. We are running 3.3.5 and our EGDB are still on ArcSDE 10.9.1. I wish someone from ESRI would chime in, @Robert_LeClair ? 

[Robert_LeClair]

Hi @JamesTurner2 - apologies for the tardy response as I've been on vacation for 2 weeks.  So I did some digging around regarding the CShareQueue stall timeout issues at 3.3 and found a few items to consider that helped other users.

1. In the case of one customer, it was determined that a dedicated GPU with current OpenGL support was missing on their system.  Recommendation was to do update the driver or purchase a new OpenGL supported video card. based upon ArcGIS Pro 3.5 system requirements—ArcGIS Pro | Documentation
2. On your Windows PC, go to Graphic Settings, add the ArcGIS Pro.exe if not present and set the GPU preference to High Performance, toggle the Optimizations for windowed games on.
3.  Disconnect the PC from the network and try to open the project.  Although IF the *.aprx is on the OneDrive network, then clearly this would not work.

Let me know what you discover - I'd be happy to assist further.

[JamesTurner2]

Thanks Robert. We are running Pro 3.3 on RDS in Azure, soon transitioning to a VDI deployment. As a result of that, I can't test 3 and number 1 and 2 really need someone from our IT department to be involved. I have passed on the recommendations. I was able to see what type of GPU the RDS is running, but I was unable to confirm if the drivers were up to date or not. I get this same time out issue on a local install of pro 3.3, but I don't have a dedicated GPU, so it's hard to say if I am getting the time out due to the same underlying issue or not. 

We do not use oneDrive for GIS work, it is all saved on an on-prem server (not in Azure). 

[waterschapVallei_en_Veluwe]

Iit seems only to happen with open Attribute Table of feature classes with SDO_GEOMETRY geometry storage. I tried to reproduce the problem with feature classes with ST_GEOMETRY geometry storage, but was unable to reproduce it!

The feature classes with SDO_GEOMETRY geometry storage are also traditional full versioned. I tried it also with unversioned feature classes with SDO_GEOMETRY geometry storage. Also in that case I can reproduce the "hang"-problems, but it looks that it is more difficult to reproduce.