Discussions

News: Gil Tene on Scaling the Java Application Footprint in Production

  1. Software platforms appear dangerously stagnant in footprint growth in recent years. The typical server application had historically grown at approximately 100 times per decade for quite a while (from 10MB in the early 1990s to 1GB in the early 2000s). Software had easily matched the predictably free growth in available hardware resources, fueled by Moore's law. Application designers that ignore this trend can fade into obscurity at an equally predictable rate. Historical rates of application footprint growth call for current, typical server application instances in the 10GB-40GB range, but since around 2001, footprint growth appears to have slowed down dramatically. In this session Gil Tene examines the main causes of current footprint stagnation and Azul's mission to remedy those causes. He describes how the Azul JVM, available on Linux, Solaris, Windows, HPUX, and AIX platforms, unlocks the power and potential that already abundant resources can bring to servers applications. Gil demonstrates how new, aggressive uses of already abundant compute capacity by common applications offer competitive value for application designers - using examples from common Azul production deployments, smoothly running Java instances with 10s and 100s of GB, discussing the scale, performance, and architecture benefits that such memory footprints are being effectively used for. Watch Tech Talk

    Threaded Messages (2)

  2. Scaling Java in Production[ Go to top ]

    Today I'm just doing that: scaling Java Footprint in my Application. To zero. In Oracle's hands, Java is going to have the same relevance .Net has: a proprietary technology in the grasp of a greedy master. DANG Dang DANG. Don't ask for whom the bell tolls, Javoid. It's tolling for you. R
  3. save your fud[ Go to top ]

    Rupert, your FUD is, like your login name, N/A. Your comment is completely baseless. We would like intelligent comments on theserverside. If you can't do better than that, please refrain. As Oracle presents it, their intention with Sun/Java is to: "Enhance Oracle’s commitment to open standards and choice". Of course, they see themselves as being front and center of that choice - they have a business to run, after all. But the promise of openness is that the Java platform will continue to be compatible regardless. If they in any way reduced the openness of Java as a platform, they would alienate half of their own customers as well as most of the customers they have bought through Sun. I don't think any company on earth would be so foolish, except maybe a US car manufacturer.