Community
Participate
Working Groups
Resources should support performance analysis and probing, so that 3rd party plugins can be notified of performance constraints while working with workspace resources.
Here's the use-case that is driving this feature for us: Some of our customers are working with projects off slow network drives (typically, ClearCase repositories). Unfortunately, many Eclipse feature assume that accessing the file system in a project is very fast, and routinely access the core.resource API from the main thread, and cause very poor usability. Worse, it is practically impossible for the user to discover which of the very numerous Eclipse preferences should be tweaked in order to improve Eclipse's UI responsiveness. Our solution for this issue has been the following additions: 1) A probing mechanism in core.resources that allow 3rd party plugins to monitor performance characteristics of workspace operations at runtime. (This is what this bug is about) 2) A plugin (lets call it usabilityOptimizer) that installs a core.resources probe, and detects when the user is working with projects located on slow file systems. When the usabilityOptimizer detects that the user is working on slow file systems, it displays this condition to the user, and informs him that some preferences can be disabled, or adjusted, in order to improve the usability of the IDE when working with slow file systems. The usability optimizer exposes an extension point to let 3rd party plugins contribute which preferences should be changed, and how. By this mechanism, when the users are working with projects located on slow file systems, the IDE can adjust automatically its preferences, and be responsive to the user.
Not sure about this one. Is it still planned for 3.7?
Unfortunately, it looks like I won't be able to make it by 3.7 timeframe.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
