Increasing latency

BrianHunt1

Over the past few weeks myself and others working on ArcPro geologic map projects have noticed an increasing latency. We can create point and lines for perhaps an hour, but then it becomes increasing slow where points show up many seconds after a click. The issue is temporarily solved if we close the program and reopen, only to have to do it again within 30-60 minutes. Really frustrating and inefficient. This seems to be a recent development. We've tried some of the basics like clearing caches and working from local drives etc.

thoughts?

RTPL_AU

@BrianHunt1 @Debert 

I've been keeping an eye on Pro in this context over the last few days - subjectively it feels as if the issue is more time driven than data driven. 
If possible, can you try something?

Open a Pro instance and something like an Esri basemap and a small number of simple layers (e.g. a boundary with a drillhole point dateset and a few pipeline lines, together giving about 200 objects over a few sqkm).
Leave that instance open for as long as you can - 1/2 a day at least, while you go about your business as usual. 
When you get back to this instance, see if it performs as expected. I am pretty sure that the longer you leave 3.5.x the slower it gets, no matter how simple or complex the data is. 

Further to this, I have now had a repeatable event that If I leave Pro open overnight (no sleep/hibernation/etc), it will be slow when I use it in the morning, and will hard crash when I try to close it (save the open project, click the X to close and the Pro window will go black, then crash).
--I'm not in the habit of leaving important stuff open overnight but things happen and you might step away for a few minutes that become a few hours.