|
Helping ordinary people create extraordinary websites! |
Java Theory and Practice: Anatomy of a Flawed MicrobenchmarkBy Brian Goetz2005-04-27
Resources • Participate in the discussion forum on this article. (You can also click Discuss at the top or bottom of the article to access the forum.) • Read the complete Java theory and practice series by Brian Goetz. December's column, Dynamic compilation and performance measurement, explores why it is that writing microbenchmarks for Java programs is so much harder than it is with statically compiled languages like C. • Jack Shirazi and Kirk Pepperdine look at some of the subtleties involved in Micro performance benchmarking Java programs (developerWorks, December 2003). • Learn more about the new locking primitives in JDK 5.0 in More flexible, scalable locking in JDK 5.0 (developerWorks, October 2004). • Want to know how synchronization is implemented? Thin Locks: Featherweight Synchronization for Java by David F. Bacon, Ravi Konoru, Chet Murthy, and Mauricio Serrano, shows some of the optimizations possible for reducing the cost of uncontended synchronization. • To learn more about Java technology, visit the developerWorks Java zone. You'll find technical documentation, how-to articles, education, downloads, product information, and more. • Visit the New to Java technology site for the latest resources to help you get started with Java programming. • Get involved in the developerWorks community by participating in developerWorks blogs. • Purchase Java books at discounted prices in the Java section of the Developer Bookstore. Tutorial Pages: » Is There Any Other Kind? » A Flawed Microbenchmark » Benchmark Code Doesn't Look Like Real Code » Ask the Wrong Question, Get the Wrong Answer » How to Write a Perfect Microbenchmark » Resources First published by IBM developerWorks |
|