Wiki source code of Web Applications-Development-Profiling WO Apps
Version 14.1 by Kieran Kelleher on 2008/11/12 14:23
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
10.1 | 1 | A profiler is a development tool that lets you examine memory useage and other bottlenecks in your app. |
| |
6.1 | 2 | |
| |
12.1 | 3 | === Kieran Kelleher === |
| 4 | |||
| 5 | Free and simple. I like the built-in sun monitoring tool. Java 1.5+ only. | ||
| 6 | |||
| 7 | Simply add appropriate argument to your launch configuration: | ||
| |
14.1 | 8 | [[image:config.jpg]] |
| |
12.1 | 9 | |
| 10 | After that, open your unix terminal and type jconsole which launches the monitoring console and detects running java apps. Select your app and watch it at work. I like the Memory and Threads tabs. | ||
| |
14.1 | 11 | [[image:jconsole.jpg]] |
| |
12.1 | 12 | |
| |
10.1 | 13 | === Ulrich Köster === |
| |
6.1 | 14 | |
| 15 | I've tried some of them. | ||
| 16 | |||
| 17 | For the big problems jprofiler is great. The docs are useful, the interface is good and the performance is okay. | ||
| 18 | I prefer jMechanic. It's small, free and works together with WOLips. Just some clicks to set it up. | ||
| 19 | |||
| 20 | I don't remember much about the others. Some of them don't run under MacOSX and it can take a lot of time to find how to use them together with WO. | ||
| 21 | |||
| |
10.1 | 22 | profiler homepage: [[http://www.ej-technologies.com/products/jprofiler/overview.html]] j |
| 23 | jmechanic homepage: [[http://sourceforge.net/projects/jmechanic/]] | ||
| 24 | to see jmechanic in action click on the profiler link: [[http://objectstyle.org/woproject/gallery.html]] | ||
| |
6.1 | 25 | Ulrich |
| 26 | |||
| |
10.1 | 27 | === Chuck Hill === |
| |
6.1 | 28 | |
| 29 | If profiling on Windows is an option, you might also want to look at jSprint: | ||
| |
10.1 | 30 | [[http://www.javaperformancetuning.com/tools/jsprint/index.shtml]] |
| |
6.1 | 31 | |
| |
10.1 | 32 | It is shareware, US$50. I've used it and was satisfied with it. It seems like a good deal for the price. I've not (yet) used jMechanic, so I can't compare the two. |
| |
6.1 | 33 | |
| |
10.1 | 34 | Before you buy anything or try anything you would be well advised to spend a couple of hours at the above Java Performance Tuning site reading up on it: [[http://www.javaperformancetuning.com/index.shtml]] |
| |
6.1 | 35 | There is a lot of good information there. |
| 36 | |||
| |
10.1 | 37 | === David Hrivnak === |
| |
6.1 | 38 | |
| 39 | (As of March 2007 the J-Sprint link above does not seem to work - the software may not be available anymore) | ||
| 40 | None of the tools on this page appear to work with WebObjects 4.5.1 on Windows. | ||
| 41 | |||
| |
10.1 | 42 | === Mike Schrag === |
| |
6.1 | 43 | |
| 44 | I use [[JProfiler>>http://www.ej-technologies.com/products/jprofiler/overview.html]] from [[ej-technologies>>http://www.ej-technologies.com]]. It works as well as any of the other big named profilers, and it has explicit support for WebObjects. It is, however, not free like some of the other suggestions. | ||
| 45 | |||
| |
10.1 | 46 | === Pierce T. Wetter III === |
| |
6.1 | 47 | |
| 48 | The CHUD tools (i.e. Shark) work on Java. |