Java Performance Tuning

Java(TM) - see bottom of page

|home |services |training |newsletter |tuning tips |tool reports |articles |resources |about us |site map |contact us |
Tools: | GC log analysers| Multi-tenancy tools| Books| SizeOf| Thread analysers|

Our valued sponsors who help make this site possible
JProfiler: Get rid of your performance problems and memory leaks! 

News May 2007

JProfiler
Get rid of your performance problems and memory leaks!


Java Performance Training Courses
COURSES AVAILABLE NOW. We can provide training courses to handle all your Java performance needs

Java Performance Tuning, 2nd ed
The classic and most comprehensive book on tuning Java

Java Performance Tuning Newsletter
Your source of Java performance news. Subscribe now!
Enter email:



JProfiler
Get rid of your performance problems and memory leaks!


Back to newsletter 078 contents

Capacity management is about optimizing the overall balance of the resources available currently and in the future for your system - including considering the hardware, the software, and the monetary and power budgets. Performance tuning fits into capacity management as a tool to more effectively utilize the resources available, and to minimize the resources that are needed. And those of you who need to consider the wider capacity management picture are saying pretty much the same thing - capacity requirements are increasing linearly overall (even including all the effort to keep down those requirements); and the datacenters keep getting full all too quickly.

That linear increase can only be reduced by making the software work more effectively on the available resources - and that's the responsibility of the performance tuning community. But ultimately information technology is such a win that there is still going to be a need to expand those full datacenters for quite a while yet. And on that front, it would be ideal if there was a way to incrementally expand the datacenter instead of guessing what we need in the future, and building as big a datacenter as we can afford. And with a simple idea, Sun have just done that. It's called Project Blackbox (at the moment, the name will change soon). I recently had the opportunity of a preview, and I concluded that here is one of those deceptively simple ideas that is going to make a big difference. To put part of a datacenter in a standardized shipping container is such a simple and powerful idea - and note that it doesn't need to be stocked with Sun kit, you can put any hardware in there that fits on the racks, just like any datacenter. In one swell foop, Sun have a solution to incremental datacenter expansion; to modular datacenter improvements; to enhanced disaster recovery support; to datacenter location changes; to datacenter support in remote locations.

A note from this newsletter's sponsor

Wily Technology delivers what you need: Availability, Performance and Control
The most critical web applications in the world are managed by
software from Wily, the leader in enterprise application management

The biggest effect is going to be on Sun of course. I had previously said that Sun can't exist as a hardware seller, and that they need work out how to make money from Java. I was wrong. Here they have re-invented themselves again, and I expect them to make good money out of this idea. But looking further into the future, is this the beginning of the end of Sun? The mix of businesses is already a real melange and if, as I suspect, the shipping container datacenter takes off as a significant reveue earner, then breakup would look to be inevitable as the parts would be worth more separately than together: the various sections of Sun would be worth significantly more with a variety of companies (e.g. Dell or HP with the containers, Oracle or IBM with Java, Red Hat to integrate Solaris into Linux, and the servers going to the inevitable Chinese company looking to move into higher end server hardware). Java itself would be unaffected by a breakup of Sun, which is a measure of how far it has come. Interesting, don't you think?

Now on with the rest of our newsletter. Of course we have our usual news, article links, tools, and extracted tips. Over at fasterj.com, we look at Su Doku solving efficiency; Javva the Hutt continues to tell us all about how he got his new job; and, of course we have extracted all the tips from those articles. And yet another treat for this month, we have a tool report from eoLogic on their eoSense analysis tool.

A note from this newsletter's sponsor

Symantec i3 for J2EE helps you optimize application performance through
out the application life cycle. Its unique adaptive instrumentation
auto-adapts to application changes. Download an eBook on J2EE performance

News

Java performance tuning related news.

Tools

Java performance tuning related tools.

A note from this newsletter's sponsor

New Steven Haines white paper explains the benefits of continuous
performance management. Proactive performance testing and continuous
integration result in optimized applications. Read the Quest paper.

Articles

Jack Shirazi


Back to newsletter 078 contents


Last Updated: 2017-11-28
Copyright © 2000-2017 Fasterj.com. All Rights Reserved.
All trademarks and registered trademarks appearing on JavaPerformanceTuning.com are the property of their respective owners.
Java is a trademark or registered trademark of Oracle Corporation in the United States and other countries. JavaPerformanceTuning.com is not connected to Oracle Corporation and is not sponsored by Oracle Corporation.
URL: http://www.JavaPerformanceTuning.com/news/news078.shtml
RSS Feed: http://www.JavaPerformanceTuning.com/newsletters.rss
Trouble with this page? Please contact us