CodePro Profiler allows you to find performance bottlenecks, memory leaks and threading issues in a painless and intuitive manner.
Moderators: gnebling, jwren, Eric Clayberg, Dan Rubel, Brian Wilkerson, ppetrochenko, Ilya
One feature I really thing is swell about your product is the ability to profile only a few classes from the project. However, I am having difficulties.
Remote profiling with "default" excluded sun/ibm/etc classes works great(byte code instrumentation does dog down very fast boxes). Well, get lots of data.
My problem: remote profiling with "selected" classes fails to gather ANY data.
My approach (maybe you will see a flaw in my approach?)
Our project is a "tomcat" project with jsp/servlets.
1) Launch eclipse ganymede. (eclipse. jvm 1.6.0_07)
2) project->profile with code pro as->remote profiling.
3) profiling mode: byte code ->configure filters.
4) "Exclude packages from profiling" dialong, remove all. (remove all the default sun,ibm, etc)
5) click "configure using workspace" button.
6) Dlg with title "please select elements that SHOULD be instrumented.
-I choose my packages carefully. Only those that I am interested in.
7) Now, the "Exclude packages from profiling" dialog list those packages that I just "included".
-THIS seems odd to me. The classes I just INCLUDED are listed in the excluded box...
-This seems like the problem to me.
8 ) Launch the profiler.
9) Launch the tomcat with the VM args per the profiler. Agent/tomcat connect, all is good.
-Again, using "default exclusion" filters, works and returns tons of data. Too much data. Just care about certain things.
Maybe you can see a flaw in my approach? Please advise. THNKS!
- Posts: 1
- Joined: Tue Aug 12, 2008 1:38 pm
- Posts: 3
- Joined: Sun May 25, 2008 10:05 am
Return to CodePro Profiler
Who is online
Users browsing this forum: No registered users and 1 guest