|
|
|
Back to newsletter 043 contents
First of all, if you have a J2EE application performance management (APM) solution that you want to have included in my upcoming review, contact me ASAP. I'll be looking at all segments of performance management over several articles, so don't miss out on being referenced.
Next, those of you who may be interested in meeting me, or winning a free copy of my Java Performance Tuning book should pop on over to the Application Performance page where you can register to attend my talk in London or Reading (UK) next month. I'll be delighted to meet anyone who can attend.
We are also delighted like to announce the availability of public Java performance tuning training courses. Our first courses are being arranged for Toronto, Stockholm, and Frankfurt. Please contact us about your interest in any of these courses.
In the newsletter we list our usual raft of articles, news, and more. In the news, yet another Java vs C++ benchmark generated a lot of heat, this time with the C++'ers deperately crying foul as Java seems to outperform. Our opinion here at JavaPerformanceTuning.com is that such benchmarks are essentially useless: Java is fast enough for anything you might want to do, and is much more productive than any other significant language.
And in the articles, JavaWorld is definitely back: they produced some good articles listed last month, and an even better one is listed this month. In addition, we have most of our usual sections. Kirk's roundup covers some interesting discussions; Javva The Hutt comes back with his latest diary entry, bemoaning his inability to wangle a JavaOne trip; And our question of the month asks What memory to measure when you are monitoring the JVM.
This month our article is a tool report, showing what DevStream's JView J2EE performance monitoring tool can do. We also have a new cartoon, and many new performance tips extracted in concise form.
Java performance tuning related news.
Back to newsletter 043 contents