JProfiler vs. JProbe
My team is thinking about getting a profiling tool. Does anybody have any experience with either tool? What are your thoughts about each one? - Do you Yahoo!? Yahoo! Movies - Buy advance tickets for 'Shrek 2'
Which is better? JProfiler vs. JProbe
tom ly [EMAIL PROTECTED] wrote:My team is thinking about getting a profiling tool. Does anybody have any experience with either tool? What are your thoughts about each one? - Do you Yahoo!? Yahoo! Movies - Buy advance tickets for 'Shrek 2' - Do you Yahoo!? Yahoo! Movies - Buy advance tickets for 'Shrek 2'
Re: JProfiler vs. JProbe
my biased perspective, Borland OptimizeIt is better than JProbe. the last time I tried to use JProbe to profile Tomcat 4 it was ungodly slow. it's probably improved since then. peter tom ly [EMAIL PROTECTED] wrote: My team is thinking about getting a profiling tool. Does anybody have any experience with either tool? What are your thoughts about each one? - Do you Yahoo!? Yahoo! Movies - Buy advance tickets for 'Shrek 2' - Do you Yahoo!? Yahoo! Movies - Buy advance tickets for 'Shrek 2'
RE: JProfiler vs. JProbe
Hi, They're both decent. I like OptimizeIt better than both of them, though. It's a personal preference as the feature lists are nearly identical. Yoav Shapira Millennium Research Informatics -Original Message- From: tom ly [mailto:[EMAIL PROTECTED] Sent: Thursday, May 13, 2004 11:19 AM To: [EMAIL PROTECTED] Subject: JProfiler vs. JProbe My team is thinking about getting a profiling tool. Does anybody have any experience with either tool? What are your thoughts about each one? - Do you Yahoo!? Yahoo! Movies - Buy advance tickets for 'Shrek 2' This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JProfiler vs. JProbe for AXIS webservices?
Sorry, I should of been more specific. Our application is huge AXIS webservices (no typical servlets here) running remotely on a non GUI (all command line) Linux box and we are telneting into the box from a windows pc. Can OptimizeIt be running from a non GUI Linux box, but have statistics shown from a windows box? Peter Lin [EMAIL PROTECTED] wrote: my biased perspective, Borland OptimizeIt is better than JProbe. the last time I tried to use JProbe to profile Tomcat 4 it was ungodly slow. it's probably improved since then. peter tom ly wrote: My team is thinking about getting a profiling tool. Does anybody have any experience with either tool? What are your thoughts about each one? - Do you Yahoo!? Yahoo! Movies - Buy advance tickets for 'Shrek 2' - Do you Yahoo!? Yahoo! Movies - Buy advance tickets for 'Shrek 2' - Do you Yahoo!? Yahoo! Movies - Buy advance tickets for 'Shrek 2'
Re: JProfiler vs. JProbe for AXIS webservices?
I honestly couldn't tell you. You'll have to look at the specs of OptimizeIt. I normally test and profile everything on my laptop, which has 1gb of ram. I wouldn't run any profiler on anything less than 1gb. peter tom ly [EMAIL PROTECTED] wrote: Sorry, I should of been more specific. Our application is huge AXIS webservices (no typical servlets here) running remotely on a non GUI (all command line) Linux box and we are telneting into the box from a windows pc. Can OptimizeIt be running from a non GUI Linux box, but have statistics shown from a windows box? Peter Lin wrote: my biased perspective, Borland OptimizeIt is better than JProbe. the last time I tried to use JProbe to profile Tomcat 4 it was ungodly slow. it's probably improved since then. peter tom ly wrote: My team is thinking about getting a profiling tool. Does anybody have any experience with either tool? What are your thoughts about each one? - Do you Yahoo!? Yahoo! Movies - Buy advance tickets for 'Shrek 2' - Do you Yahoo!? Yahoo! Movies - Buy advance tickets for 'Shrek 2' - Do you Yahoo!? Yahoo! Movies - Buy advance tickets for 'Shrek 2' - Do you Yahoo!? Yahoo! Movies - Buy advance tickets for 'Shrek 2'
RE: JProfiler vs. JProbe for AXIS webservices?
I have installed OptimizeIt on one Windows system and deployed the needed profiling runtime to a remote Windows system. I was able to attach to and profile an application on the remote system. I would assume you would be able to do the same with a remote Linux system. The OptimizeIt 5.5 I installed included documentation about starting the remote test application on a Unix system as well as on Windows. Cheers, Larry -Original Message- From: tom ly [mailto:[EMAIL PROTECTED] Sent: Thursday, May 13, 2004 11:37 AM To: Tomcat Users List Subject: Re: JProfiler vs. JProbe for AXIS webservices? Sorry, I should of been more specific. Our application is huge AXIS webservices (no typical servlets here) running remotely on a non GUI (all command line) Linux box and we are telneting into the box from a windows pc. Can OptimizeIt be running from a non GUI Linux box, but have statistics shown from a windows box? Peter Lin [EMAIL PROTECTED] wrote: my biased perspective, Borland OptimizeIt is better than JProbe. the last time I tried to use JProbe to profile Tomcat 4 it was ungodly slow. it's probably improved since then. peter tom ly wrote: My team is thinking about getting a profiling tool. Does anybody have any experience with either tool? What are your thoughts about each one? - Do you Yahoo!? Yahoo! Movies - Buy advance tickets for 'Shrek 2' - Do you Yahoo!? Yahoo! Movies - Buy advance tickets for 'Shrek 2' - Do you Yahoo!? Yahoo! Movies - Buy advance tickets for 'Shrek 2' - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JProfiler vs. JProbe
From: tom ly [EMAIL PROTECTED] Sent: Thursday, May 13, 2004 8:18 AM My team is thinking about getting a profiling tool. Does anybody have any experience with either tool? What are your thoughts about each one? I've had mediocre success with any of them. They all seem to basically do the same thing, they're all pretty darn slow, and they've never really told us much that we didn't know already. With our J2EE app, a lot of our issues turned out to be contention in the container, something none of these tools were able to narrow down, isolate, or identify (even some of the $$$ enterprise tools). I've tried these tools, yet I still have better luck with strategically placed Log4J statements, occasional thread dumps, and verbose GC chatter. Even the stock hprof is basically usable, once you get the hang of it. It's not that the tools aren't good, its just, to me, for the money, they're not a good value over things that are readily available. As a developer, you typically KNOW what's slow anyways, and a bit of logging instrumentation goes a long way. If user X clicks on button Y and it feels slow, that alone narrows down the problem. For monitoring some behaviors, try BEA JRockit, it comes with a nice memory profiler system built in. It also has a method profiler. Finally, if you're looking for production logging, none of the tools mentioned will help there at all. They're too expensive (performance wise) to run. If you have NO IDEA why you code is slow, these tools MAY help you. But in that case they overwhelm you with so much data, that it's pretty much hopeless. Wow, StringBuffer is the culprit. Yea, that's real helpful information. We only call it 8000 times throughout the app. It takes diligence and patience to tune your app, tune it one piece at a time, make sure you can duplicate your results through load testing, and make sure you only tweak one knob at a time, otherwise you may not know what made it faster/slower. Tune early, tune often. One of the things we did was we wrote our own logging JDBC layer (they are all simply interfaces, after all) which checks how long SQL queries take, and logs those that hit a specific threshold. Dumps the SQL, dumps the bind, whole ball of wax. Then we can go through that log on a regular basis to tune queries, the DB, or the code. That helped a LOT for our system. Regards, Will Hartung ([EMAIL PROTECTED]) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JProfiler vs. JProbe
have any of you taken a look at hyades? http://www.eclipse.org/hyades/ Will Hartung wrote: From: tom ly [EMAIL PROTECTED] Sent: Thursday, May 13, 2004 8:18 AM My team is thinking about getting a profiling tool. Does anybody have any experience with either tool? What are your thoughts about each one? I've had mediocre success with any of them. They all seem to basically do the same thing, they're all pretty darn slow, and they've never really told us much that we didn't know already. With our J2EE app, a lot of our issues turned out to be contention in the container, something none of these tools were able to narrow down, isolate, or identify (even some of the $$$ enterprise tools). I've tried these tools, yet I still have better luck with strategically placed Log4J statements, occasional thread dumps, and verbose GC chatter. Even the stock hprof is basically usable, once you get the hang of it. It's not that the tools aren't good, its just, to me, for the money, they're not a good value over things that are readily available. As a developer, you typically KNOW what's slow anyways, and a bit of logging instrumentation goes a long way. If user X clicks on button Y and it feels slow, that alone narrows down the problem. For monitoring some behaviors, try BEA JRockit, it comes with a nice memory profiler system built in. It also has a method profiler. Finally, if you're looking for production logging, none of the tools mentioned will help there at all. They're too expensive (performance wise) to run. If you have NO IDEA why you code is slow, these tools MAY help you. But in that case they overwhelm you with so much data, that it's pretty much hopeless. Wow, StringBuffer is the culprit. Yea, that's real helpful information. We only call it 8000 times throughout the app. It takes diligence and patience to tune your app, tune it one piece at a time, make sure you can duplicate your results through load testing, and make sure you only tweak one knob at a time, otherwise you may not know what made it faster/slower. Tune early, tune often. One of the things we did was we wrote our own logging JDBC layer (they are all simply interfaces, after all) which checks how long SQL queries take, and logs those that hit a specific threshold. Dumps the SQL, dumps the bind, whole ball of wax. Then we can go through that log on a regular basis to tune queries, the DB, or the code. That helped a LOT for our system. Regards, Will Hartung ([EMAIL PROTECTED]) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Emerson Cargnin Analista de Sistemas Setor de Desenvolvimento de Sistemas - TRE-SC tel : (048) - 251-3700 - Ramal 3181 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
