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 "use" ArcGIS Pro 3.3 and it has become so incredible slow that I now strated to use my old ArcGIS 10.8.1 to get some work done. Then I thought the old version was slow but not compared to the Pro 3.3. I have for sure not layers that are "optimised" as the guides are in Pro 3.3 - but still it's totally unacceptable slow. My data is not on cloud in that sence but on a server located out of office.

[HollyTorpey_LSA]

Apologies for not seeing your response sooner. It's interesting to know that you're having the same issues using data stored on non-cloud servers.

[The_geologist18]

I'm in the same boat. Pro 3.3, projects have been moved to the "cloud". Took 10min 49sec to convert a small set of labels (20) to annotation. Renaming features takes 2-5 minutes. Run time on most tools has increased by 10x. I've resorted to moving everything to my local drive, and repathing all 300+ features in my .gdb. What should take me 1 hour, now takes a full 9hr day unless my project and maps are moved locally. What a joke ESRI..

[HollyTorpey_LSA]

@The_geologist18  Your experience sounds very much like what we are experiencing. It's soul crushing to have to wait so long after simple operations like renaming a map or layer, changing symbology, etc. We also have noticed frequent issues of being unable to save edits (with a read-only error) only to repeat the operation successfully a moment later. It's really challenging to figure out whether the issue is Pro, our Cloud storage system (Nasuni), our antivirus software, or our Azure VM, but the Pro users are definitely suffering far more than those still using ArcMap.

[Greg_Sikma]

We are having the same issues in my office with converting labels to annotation, running calculate fields on single records, etc. Simple actions take an extremely long amount of time. We have also had issues with tools not running correctly one minute and creating corrupted data, only to have the tool run fine a few minutes later. It is not good if I cannot trust the software to perform correctly or predictably.

I have also had similar issues with ArcPro projects not being able to save after making changes (in a local environment). Sometimes when I press "save project" it opens the "save as" dialog box with no explanation. I've taken to saving a new version (as a backup) and then overwriting the original file. Unfortunately, when working on multiple projects, the save as may not open in the directory where you opened the file from and may default to another project location. This caused me to accidentally overwrite another project file. My fault yes, but when working with multiple projects on a daily basis with similar naming conventions it can be confusing. 

It is nice that if changes in ArcPro are made in once place in the project, the software will change it everywhere to prevent broken links, etc., but should renaming something like a map or layout really take several minutes?

I've even noticed that when making some quick edits, such as typing a value in the attribute table, moving down to the next record with the cursor key, and repeating the process in rapid succession, ArcPro it will often  ignore some key strokes leaving some records null as if I am moving too fast for it to keep up. 

I have tried  a number of things, such as working with all data stored on my local workstation, but it is still very very slow. I make sure I only have one or two items (maps, layouts, attribute tables etc.) open at a time, but it is still slow. It makes working in Pro a maddening exercise in frustration. 

I have started using ArcMap 10.8.3 for many analysis tasks as they are much much faster. Unfortunately, I am tied to a project layout in ArcPro and need to push forward.

Honestly, it feels like I am testing a buggy slow beta software, rather than a very expensive "professional" software. Sorry, I have no solutions, but just know that many people share the same challenges with using extremely slow, frustrating experiences in ArcPro. 

[HollyTorpey_LSA]

Thanks for the response. We're still struggling to resolves these issues. We also have the issue of the software not "keeping up" with attribute table entries. We also frequently get read-only errors when writing data or running a geoprocessing tool, only to have the tool work moments later. I think it's related to some kind of caching or syncing operation taking place on our cloud fileshares, but our IT staff hasn't gotten to the bottom of it yet. Recently we also had issues with copying items (labels, maps, layers) taking a ridiculous amount of time (though pasting was quick). That seems to have resolved itself but no one knows why. The fluctuations and inconsistencies are possibly the most frustrating part.

[ThomasMelton_ARDOT]

We are seeing the same problems as listed by Greg and Thomas in regards to performance in 3.3. Seems especially any text rendering takes forever. I rolled back to 3.0.6 and everything was back to running properly (albeit still much slower than ArcMap). In my area we are responsible primarily for some simple cartography, but seems something definitely changed between 3.0 and 3.2 that makes it almost impossible to work because of the loss of time on a project. And we have done all the "standard" ESRI suggested fixes we have seen online, our computers are rocket ships, we updated our video drivers, we tried every optimized video setting we could find for Pro, we changed our data sources to the local hard drive (sorry this is a step back 25 years so shouldn't even be considered a solution ESRI), and when running data locally in 3.3 right next an identical machine running 3.0 sourcing data on SDE on MSSQL server, it is like running in quicksand with 3.3. We are supposed to have a call with ESRI engineers in coming days, I am hoping for solutions to our issues. I speak with other professionals that do similar tasks in other agencies and they are having the same problems. My point will be, same data, same machines, the ONLY change is "upgrading" to 3.3. AGAIN I want to stress, the only change is the version of ArcGIS Pro. I want to upgrade to 3.3, I want to stay current, I want the new gadgetry, but if we can't do our primary simple cartography tasks, we cannot justify it.

[JamesThompson_PEC]

Were you able to speak to your ESRI rep/ESRI engineers? Are you still experiencing issues? 

I too did the same thing and upgraded to the latest version, and even with the most recent patch things were colossally slow. It was so bad that I rolled back to 3.1. I'm afraid to update to anything 3.3.x simply because the issues are too great. I'm not versed enough in anything outside of GIS tasks to really be able to tackle the issue but I am glad I came upon this thread and saw solutions to just roll back to an older version of ArcGIS Pro. Really not great for ESRI, but it is expected at this point that major things are going to be wrong even after a couple patches. 

[ThomasMelton_ARDOT]

They scheduled out meeting for the first week in November. They also asked us for our hardware configs, and to run the "Verify your computer's ability to run ArcGIS Pro" tool. They also requested we look at the Diagnostic Monitor and see if we can capture the logs for them to review before hand for any thing obvious. I noticed some of the Aux CIM worker threads where giving a CSharedQueue Stall timeout, whatever that means. We are still collecting as much information as possible to send in. I will hopefully find something out in a month.