How to check the performance of the Eclipse plugin

Question

I am new to Eclipse plugin development.

I modified the plugin that was used in our team, and I do not want to add new bottles.

Also the eclipse to which I integrate takes too much time to install the plugin. Any suggestion on how to determine the cause of this?

So, I would like to know some tips about

• How to check plug-in performance - any tools available. (e.g. jprofiler in java or any other performance analyzer tool)
• How to check a bottleneck in my plugin code with some tools.

And is there a document that tells what to do, and not about the development of the plugin.

Answer 1

Studying plug-in performance is not so different from any regular Java program. It works in a similar way. For example, see this question .

It takes a long time to install; It seems like this will be the problem of the underlying P2 program, not your plugin. When you install the plugin, your manifest is read, some information about your extensions is stored in Eclipse. The actual plugin is copied. Dependencies checked. It seems that these things should not last so long if you do not have a very large plugin? Perhaps you are installing the plugin in an environment that already has the plugin? Try downloading pure Eclipse, do you have the same problem?

Make sure your plugin does not start automatically when the user starts Eclipse. This is bad behavior that causes confusion and a general slowdown for users. The plugin should be launched when the user really wants to use it, and not a second ago.

Also my answer to this question may help with the overall plugin design.

Answer 2

First of all, measure everything, since you should never try to optimize just by guessing the performance bottlenecks. I recommend Yourkit for all Java code (Eclipse plugins as well as plain Java code).

The second important thing: if you have functionality that takes longer than a blink of an eye, do this job in Eclipse , so it can run in the background. It is normal to start a few seconds if this does not prevent the user from working.