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.
