Fix lag time in Attributes and Traverse

[anna_garrett]

There is a significant lag in the time between I enter a value in the Attributes menu and it actually accepting that value, going through the whole ordeal of redrawing everything, and being done with it to move on. In my street centerlines, I have four rows: L_ADD_TO, L_ADD_FROM, R_ADD_TO, R_ADD_FROM. I put in one value and I've typed this post while I'm waiting to add another one. This has not been an isolated incident and I've been dreading updating my centerlines since I started migrating to Pro because I have a lot of updates this year. 

I've also encountered a similar lag issue when entering traverses that are more than just four lines. Drawing creek meanders is far far slower than in ArcMap, for instance, where there can easily be 15+ calls. It appears that Pro is checking through every single line I've entered as soon as I enter another one and it's simply inefficient. 

[anna_garrett]

@AmirBar-Maor

https://community.esri.com/t5/arcgis-pro-ideas/pause-auto-commit-during-traverse-in-pro/idi-p/936677 please check this out, as it's the exact problem i'm having as well. it's from last year.

[AmirBar-Maor]

@anna_garrett 

This issue was reported in ArcGIS Pro 2.6 and got resolved in version 2.8 (or 2.7 not sure).

Which version are you using?

Did you call technical support? (always recommended)

Are you using feature services?

Do you have network issues?

[KoryKramer]

@anna_garrett since you say the exact problem you're having is https://community.esri.com/t5/arcgis-pro-ideas/pause-auto-commit-during-traverse-in-pro/idi-p/936677 we're closing this duplicate idea.  

I'm checking in with the Editing team to see if we can get more information about any improvements that may have been made in this area, but if you are already using Pro 2.8 and are still experiencing issues, we would need more information about the data, network, etc. as Amir is asking on this and the other thread.

While it may not address the specific latency you're experiencing, you could run through Troubleshooting Performance Issues in ArcGIS Pro Note that it points to the Pro Performance Assessment Tool (PAT) which can help benchmark the machine against typical ranges to run the tool.  However, we'll also need to understand what data you're working with (feature services?) and whether that may be introducing lag.  It might be most helpful to work with technical support rather than trying to troubleshoot through an Idea.