tag:blogger.com,1999:blog-8329194600626179521.post6973255155355685503..comments2008-09-16T15:20:16.304-04:00Nick Maioranonoreply@blogger.comBlogger2125tag:blogger.com,1999:blog-8329194600626179521.post-17071079098072351842008-09-16T15:20:00.000-04:002008-09-16T15:20:00.000-04:00

One of the most useful tools I am really missing is a monitor statistic, which class and object have how many blocked threads for how long. This will make that kind of debugging quite easy. You can also see which synchronized blocks are actually painful and which not.<BR/><BR/>Even with sampling profilers I don't know any who can aggregate it by lock instead of by block.

eckeshttp://bernd.eckenfels.net/noreply@blogger.comtag:blogger.com,1999:blog-8329194600626179521.post-77934034594324909772008-07-07T15:30:00.000-04:002008-07-07T15:30:00.000-04:00

Why not just take some free java profiler and use sampling mode? There are lots of them.<BR/>However, there is one case where this technique is useful, namely when the application is started without -Xdebug, but I haven't seen people who have a good reason to do that for a long time.

antilamerhttp://antilamer.livejournal.com/noreply@blogger.com