Affects Version/s: None
Fix Version/s: 2.1.0
Similar Issues:Show 9 results
ECLIPSE-506 Use the new one stop JMX method to get Camel profile stats to make Fuse IDE run faster ECLIPSE-631 The processors and profile tab should have similar ids as in the diagram view, to make it easier to correlate ECLIPSE-630 Filter does not work in profile view ECLIPSE-496 route Profile view is too slow - can we optimise it? ECLIPSE-728 consider using a single table for a Profile Details view for changing profiles ECLIPSE-795 Fabric view - Delete profile requirement button does nothing ECLIPSE-908 Too easy to ruin a fabric via IDE's set profile UI ECLIPSE-898 Properties view is still refreshing when we want to see profiles of a container ECLIPSE-651 When clicking the processors or profile tab then the diagram view is cleared
With the latest RCP build of today, the JMX tree is reacting much faster, and its an enjoyment to use now.
However the Profiles View is still slow. We have a JIRA ticket about that. The reason is that its most likely using a fine grained API to gather the data.
I have added a method on the FMC facade to get all the data in 1 JMX operation.
I think we should fix this, to make it go fast like the other views.
You can see its really slow, for example by just scrolling its scroll-bars. It takes a bit to update the screen after scrolling.
And the scrollbar dont react immediately.
Unlikes the Processors view, where you can press mouse down, and move the scrollbar back/forth and it updates the screen immediately.