Eclipse Simple Profiler Ben Xu Mar 7,2011

About Eclipse simple profiler is a open source project to analyze your plug-ins/RCPs performance.

Why I begin to create this project when I try to do some performance analyze for 100+ plug-ins in my company. There are lots of java profilers in the market, both commercial and open source. But on one meeting all the following requirements: –Support analyze eclipse plug-ins/RCP development easily –Tightly integrated into the eclipse PDE environment –Support filter/specify your plug-in/class/method to be analyzed –Support start and end profile at any time –“Zero” or little performance decrease when using the profiler –Intuitive and simple enough I really don’t want to spend a whole day to learn how to use a profiler to improve performance

Write a new one? Isn’t it a good idea to write a new profiler specialized for eclipse plug-in/RCP development.

How? After several weekends, I found that it is not so difficult to write a java profiler. Actually, not difficult at all!

Architecture Plug-ins at eclipse workspace instrumented Runtime eclipse/RCP simple profiler view (runtime controller & result analyzer) Plug-ins at target platform instrumented Java boot classes Simple profiler model

Architecture The profiler contains 3 parts: –Instrument Simple profiler provides tool to instrument both plug-ins under current eclipse workspace and pug-ins in the target platform – Instrument production plug-ins at target platform will not be available first –Generated classes files are instrumented for plug-ins at workspace –Simple profiler model The plug-ins are instrumented to write detail information to the profiler model when the instrumented plug-ins run at runtime. The profiler result analyzer and runtime controller can control the profiler model and analyze this model at runtime. To make it easy for the first version. The model is put at JRE’s boot class path, instead of implementing a special run configuration. –Simple profiler result analyzer and runtime controller When the instrumented plug-ins are running, the result analyzer can show analyzed results.

The model

The profiler view Method Summary: Method name, runtime, average time, total time, %-  time distribution analyze Runtime Log: (latest limited number: flat and tree) thread, method, start,end, used time The runtime controller: