References

Bruce Eckel's Thinking in Java Contents | Prev | Next

Performance tools

[1] MicroBenchmark running on Pentium Pro (200Mh), Netscape 3.0, JDK 1.1.4 (see reference [5] below).

[2] Sun’s Java document page on the JDK Java interpreter http://java.sun.com/products/JDK/tools/win32/java.html

[3] Vladimir Bulatov’s HyperProf http://www.physics.orst.edu/~bulatov/HyperProf

Web sites

Articles

[6] Make Java fast: Optimize! How to get the greatest performance out of your code through low-level optimizations in Java by Doug Bell http://www.javaworld.com/javaworld/jw-04-1997/jw-04-optimize.html, complete with an extensive annotated measurement Benchmark applet.

[7] Java Optimization Resources http://www.cs.cmu.edu/~jch/java/resources.html

[8] Optimizing Java for Speed http://www.cs.cmu.edu/~jch/java/speed.html

[9] An Empirical Study of FORTRAN Programs by Donald Knuth, 1971, Software – Practice and Experience, Volume 1 p. 105-33.

Java specific books

General books

[12] Data Structures and C Programs by Christopher J. Van Wyk, Addison-Wesley, 1988.

[13] Writing Efficient Programs by Jon Bentley, Prentice Hall, 1982, especially p. 110 and p. 145-151.

[14] More Programming Pearls by Jon Bentley. Association for Computing Machinery, February 1988.

[15] Programming Pearls by Jon Bentley, Addison-Wesley 1989. Part II addresses generic performance enhancements.

[16] Code Complete: A Practical Handbook of Software Construction by Steve McConnell, Microsoft Press 1993, Chapter 9.

[17] Object-Oriented System Development by Champeaux, Lea, and Faure, Chapter 25.

[18] The Art of Programming by Donald Knuth, Volume 1 Fundamental Algorithms 3rd Edition, 1997; Volume 2, Seminumerical Algorithms 3 rd Edition; Volume 3 Sorting and Searching 2 nd Edition, Addison-Wesley. The definitive encyclopedia of algorithms.



Comments

  • There are no comments yet. Be the first to comment!

Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • With JRebel, developers get to see their code changes immediately, fine-tune their code with incremental changes, debug, explore and deploy their code with ease (both locally and remotely), and ultimately spend more time coding instead of waiting for the dreaded application redeploy to finish. Every time a developer tests a code change it takes minutes to build and deploy the application. JRebel keeps the app server running at all times, so testing is instantaneous and interactive.

  • Instead of only managing projects organizations do need to manage value! "Doing the right things" and "doing things right" are the essential ingredients for successful software and systems delivery. Unfortunately, with distributed delivery spanning multiple disciplines, geographies and time zones, many organizations struggle with teams working in silos, broken lines of communication, lack of collaboration, inadequate traceability, and poor project visibility. This often results in organizations "doing the …

Most Popular Programming Stories

More for Developers

Latest Developer Headlines

RSS Feeds