Bug 220546 [Decorators] performance problem with resource manager in decoaration context
20080217 I'm afraid the solution to use the IDecorationContext to provide a resource manager introduces a performance degregation. The DecoratorManager, who manages the light weight label decorations, stores decorations by context DecorationScheduler.resultCache<IDecorationContext, Map<DecorationResult>> Most label providers used the default context (DecorationContext.DEFAULT_CONTEXT). If there were several requests for the same image, all the requests were bundled and the result was only computed once before the result was broadcasted to all viewer. Now, with the new code, each label provider has its own instance of a decoration context. There will be separate computations per context. Even if two viewers want to decorate the same image, each of them will have to compute a DecorationResult The broadcast, however, still goes to all viewers.
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/DecoratingLabelProvider.java
}
		}
		return image;
	}
	/**
	 * Returns the label decorator, or <code>null</code> if none has been set.
	 * 
	 * @return the label decorator, or <code>null</code> if none has been set.
	 */
	public ILabelDecorator getLabelDecorator() {
		return decorator;
	}
	/**
	 * Returns the nested label provider.
	 * 
	 * @return the nested label provider
	 */
	public ILabelProvider getLabelProvider() {
		return provider;
	}
	/**
	 * The <code>DecoratingLabelProvider</code> implementation of this
	 * <code>ILabelProvider</code> method returns the text label provided by
	 * the nested label provider's <code>getText</code> method, decorated with
	 * the decoration provided by the label decorator's
	 * <code>decorateText</code> method.
	 */
	public String getText(Object element) {
		String text = provider.getText(element);
		if (decorator != null) {