Kai's em novo blog como um funcionário da Sun é agora o The TAO of AMP e os posts mais recentes estão começando a refletir o estilo dele: • Impulsione seu site AMP utilizando mod_rewrite • O Guia de Manga de DataBases Ainda da tempo para adicionar The TAO of AMP à sua lista de leitura diária.

Telco Application servers such as SailFin require a more deterministic GC model with predictable pause time, and also that scales well on multiple processors. Waiting for a long time to connect a telephone call is clearly unacceptable. Performance team at Sun spent a lot of time tuning GC while testing SailFin for high work loads. Bharath has written a series of blog entries (here and here) explaining his experience. Take a look.

Sun has posted SPECjAppServer 2004 results for a full OpenSource stack including MySQL 5.0, GlassFish v2 U2 and OpenSolaris 2008.05 on Sun's 1U SunFire x4150. The setup uses two x4150 running GF and one running MySQL, all on OpenSolaris. Check out the detailed posts by BMSeer and Tom (Overview and Price Analysis). Also see the SPEC detailed submission and the relevant x4150 Benchmark page. The results take advantage of recent MySQL Performance Improvements including [1], [2], [3], [4].

Note Required disclosure : SPEC and SPECjAppServer are registered trademarks of Standard Performance Evaluation Corporation. Results from www.spec.org as of 11/05/2008. 2xSun Fire X4150 (8 cores, 2chips) and 1xSun Fire X4150 (4 cores, 1 chip) 1197.10 SPECjAppServer2004 JOPS@Standard; Best result with 8 cores in application-tier of the benchmark: 1xHP BL460c (8 cores,2chips) and 1xHP BL480c (8 cores,2 chips) 2056.27 SPECjAppServer2004 JOPS@Standard; Best result with 2 systems in application-tier of the benchmark: 2xDell PowerEdge 2950 (8 cores, 2 chips) and 1xDell PowerEdge R900 (4 chips, 24 cores) 4,794.33 SPECjAppServer2004 JOPS@Standard.

A compilation of today's news of interest:

A compilation of today's news of interest:

Network Manager is a SailFin module that handles Grizzly integration, message parsing, ByteBuffers, thread pools etc. Ramesh, the module owner for network manager layer in SailFin Project, has started a series of blogs [1,2] explaining the knobs available to configure SailFin SIP container for high performance. Checkout Eltjo Boersma's blog for more details about configuration of SailFin network listeners.

On the JCP front, JSR 289 has been submitted for final approval ballot. Click here to download the latest version of the specification.

The buzz of the week is all about books. The second edition of High Performance MySQL has just hit the shelves. In addition to being a complete rewrite of the first edition, this is a sort of community book, where the authors gathered together the official tools and the ones available in the community to explain how to make MySQL fly. Many topics were submitted for public discussion. It is also the first time that an author has explained in public how to write it. The other second edition is a reprint of the MySQL Cluster certification guide. Noticed anything peculiar in the cover? Yes! It's a Sun book. This is actually the very first book to be published through Sun's new print-on-demand partner, Vervanté. In other words, Sun's first Vervanté book is a book on MySQL!

Meena has posted a quick note on how to turn on GC logging on both the Cluster and the DAS instances of the GlassFish Server; check out her note on Monitoring Memory Growth in GlassFish. I need to catch up on the whole VisualVM effort; perhaps we should invite them for the new TheAquarium TV series.

NetBeans 6.1 was just released and it is both a feature and a performance release. The feature part has to do with JavaScript support - the language everybody loves to hate (See Roberto's talk at JavaOne), MySQL improved support, Spring Framework support, Hibernate support, Axis 2, Sailfin support, and Jersey (RESTful Web Services) support.

It's also bringing back features lost in the translation from 5.5. to 6.0 such as JavaBeans support and the JSF CRUD Generator. NetBeans also now provides a more natural way to share libraries. All in all a lot of web and server-side features including support for the latest GlassFish v2ur2 release. The full list of features is here.

Performance is related to startup-time, completion speed, and memory consumption. Coming attractions include PHP support, JavaScript debugger, Groovy/Grails support, and more.

As always, the nice download matrix is available here. Congratulations to the team for yet another solid release!

Another good writeup from Scott (time trip: [1], [2], [3, [4]) this time on using NIO vs IO, partly as followup to JD Campbell's Top Java 5 EE Servers Compared. Scott compares simple and complex cases: in a simple request/response case the overhead of the select() call implied by NIO is noticeable, but in the more complex case where you need to scale, NIO is the clear winner.

Check out Scott's note and you may also enjoy browsing other entries in his blog.

Scott Oaks is the person among others in our great Java performance team behind the excellent and recent SPECjAppServer performance results for GlassFish ([1], [2]). Scott has put out a GlassFish Tuning Primer one-pager. It covers both JVM (throughput collector is suggested as the default choice for large heaps) and application server tuning (acceptor and request-processing threads, JDBC driver statement caching, etc...) and should serve as a good appetizer for our "hundreds of pages of tuning guidelines in our docset".

Here is a very nice result taking advantage of Metro's layered architecture: Use an efficient encoding (FastInfoset) and a protocol that is very good for many small packets (Stateful SOAP/TCP) and you can get as much as a 3x improvement over XML over HTTP. Click to see charts for the different tests: Small, Medium and Large. More details at Oleksiys's writeup.

Also important to point out that, thanks to Noemax, there is now SOAP/TCP Interoperability with Microsoft's Windows Communication Framework (see Announcement).

Earlier this week Sun announced new machines using the UltraSPARC T2. Many of the key contributors have written about them and Allan has a Nice Overview that links to the key posts. The new systems show great performance; check out BMSeer's Posts and the official T5220 page. One result we want to highlight is the Web Tier Benchmark posted using the Sun WebServer (using the GlassFish Java Web Tier). Check out CVR's Writeup and BMSeer's Comparisons.

Congratulations to the Sun WebServer team! And to everybody who got the systems out to market!

Santiago has posted Japex 1.1.4, the GlassFish WS and XML performance tool. The new release addresses new customers, including CORBA (the new japex.singleClassLoader property) and a multi-user simulation (japex.runIterationDelay). Rapid interaction between customers and developers is a key benefit of Transparent Development; this is a good example. Check more details in Santiago's Blog.

If you've ever had to deal with Java performance tuning, you probably know about a few supported and maybe unsupported JVM tuning flags. Jeanfrancois "Grizzly" Arcand has a set of options for you when it comes to the Grizzly configuration (most are actually startup VM properties).

Here are my top picks (all apply to GlassFish v2):
• HTTP compression
• Comet support
• snooping support (I just like logging options)
• Asynchronous Request Processing
• Resource Consumption Management

As always and similarly to the JVM tuning case, the problem with having many options to choose from is to have methodology and good reasons to try them out. With greater power comes greater responsibility.

On the topic of Grizzly, there's a short article on JavaLobby for its 1.6.1 recent release.