Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Plugin Development Environment (PDE) » Plugin Performance Troubleshooting Help
Plugin Performance Troubleshooting Help [message #586296] Wed, 03 December 2008 17:22
Eric Bresie is currently offline Eric BresieFriend
Messages: 46
Registered: July 2009
Member
Okay...in an attempt to identify where the bloat in my configuration is, I
decided to see what plugins were using the most memory and try to disable
the ones I was not using. I also suspect there are a number of plugins
that are active that I just plan do not need in my current configuration
which may also be slowing things down.

I started looking at Core Tools (Runtime Spy) to do something about it,
but documentation was a little unclear for me and I was unable to get it
working for me.

Looking around, I believe the Core Tools have now been rolled into the
another part of the platform (as I understand it under PDE or Equinox).

I would like each plugin listed and how much memory it is using, but not
sure how to do this with more recent versions.

I would like to see for a given perspective, what plugins are required and
which are not.

For example, if I am just working on a Java EE perspecitve, it does seem
likely that I need C environment related plugins or many of the dynamic
language plugins.

Looking in some of the PDE related views, there is Plugin view, a Plugin
Registry view, and Plugin Depedency view. These all seem almost exactly
alike. What is the difference between these?

Can someone provide some guidance on this with current 3.4.x
configurations? You help would be greatly appreciated.

Eric
Previous Topic:Clean product builds?
Next Topic:Keep having the ClassNotFoundException with RCP product launch
Goto Forum:
  


Current Time: Wed Jul 28 19:21:07 GMT 2021

Powered by FUDForum. Page generated in 0.01311 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top