Why does your application run so slowly? I bet you think it's the algorithms or the fact that you are starting all your services instead of using extension points. It runs so slowly because there is a fat man sitting on it. No one can run fast when they are carrying that much dead weight.
Experience has shown me that the performance problems are never where I expect them to be. The things that I initially think will be problems often never even show up in the trace, and code blocks that I can't believe often dominate the execution time. Over time I have found many of same blocks showing up very high in the trace. These are fat men and they need to be removed before we can find the performance problems in our algorithms. In this talk we will look at profiling a real world embedded Java/OSGi application to remove the fat men, and maybe even some of algorithm problems in my code. The application ran fine on my laptop but took over a minute to start and ran out of memory when put on its intended embedded target. By the time it was deployed it started up fine, and ran for days without running out of memory. It will be part experience report, part best practices, all fun!
This video was recorded at EclipseCon 2009.
Total running time 30:50 minutes
delicious | 
digg | 
dzone
Votes: 1
Comments