Re: [eclipse-pmc] API Request: additional method for caching changes

[Mike Wilson <Mike_Wilson@xxxxxxxxxx>]

+1 for M7. This helps to address a significant
performance degradation (that users are noticing) in the new command support.

McQ.

Paul Webster/Ottawa/IBM@IBMCA
Sent by: eclipse-pmc-bounces@xxxxxxxxxxx

03/28/07 11:14

Please respond to
eclipse-pmc@xxxxxxxxxxx

To	eclipse-pmc@xxxxxxxxxxx
cc
Subject	[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.


_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc