-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Batch FAR window update messages to lower refresh overhead. #73534
Conversation
@ToddGrun ptal |
// Similarly, updating the actual FAR window can be quite expensive (especially when there are thousands of | ||
// results). To limit the amount of work we do, we'll only update the window every 500ms. | ||
_notifyQueue = new AsyncBatchingWorkQueue( | ||
DelayTimeSpan.Medium, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I kind of feel like I wish the ABWQ had an option where it would customize the delay as the work expanded.
Something like:
For the first 1 second, it updates on NearImmediate cadence.
Between 1 - 5 seconds, it updates on short cadence
After 5 seconds, it updates on medium cadence
It just feels like adding a 500 ms delay on really quick FAR requests might be perceptible.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I def didn't notice anything feeling off here. I could make it 250ms if you feel better about that. We'll still likely get the majority of the benefit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would like that. 250 ms is a lot less noticeable than 500 ms.
src/VisualStudio/Core/Def/FindReferences/Contexts/AbstractTableDataSourceFindUsagesContext.cs
Outdated
Show resolved
Hide resolved
src/VisualStudio/Core/Def/FindReferences/Contexts/AbstractTableDataSourceFindUsagesContext.cs
Outdated
Show resolved
Hide resolved
@ToddGrun done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Drops CPu utilization in Devenv from 57Msecs in an expensive FAR scenario:
to just 34Msecs
--
While the FAR window is good, it's not good enough that thousands of notification updates dont' impact it.