|[eclipse-pmc] API Request: additional method for caching changes|
The context service fires one event for each context that is added or removed, even when a number of changes were all caused by the same source change event, like a workbench window activation. This is currently causing way too many binding re-evaluations. This is API because the ContextManager is in org.eclipse.core.commands. I want to add ContextManager#setEventCaching(boolean). GOALS/BENEFITS: Reduce churn in the system by firing one event for all context changes occurring because of one source change. CORRESPONDING BUG: https://bugs.eclipse.org/bugs/show_bug.cgi?id=179036 RISKS: This is low risk, as it's a new method to allow batching of change events. PERFORMANCE IMPACTS: This will improve the context updates incurred because of Shell activation from around 500ms to about 80ms. It will also reduce the amount of caching the in the BindingManager.
Back to the top