« Servlet/JSP applicat... | Main | Defending Struts »

On the topic of System.out.println

Comments[0] by Dave in Java

Erik pointed to the Log4J write-up titled Don't Use System.out.println the other day and yesterday it was the hot story on Javablogs (I kid you not). This does not really have anything to do with Log4J, but here is what the Webpshere best practices paper that I mentioned earlier says about using System.out.println in a web application:

Minimize use of System.out.println.  Because it seems harmless, this commonly used application development legacy is overlooked for the performance problem it really is. Because System.out.println statements and similar constructs synchronize processing for the duration of disk I/O, they can significantly slow throughput.
I did not know that.


Like this post?  del.icio.us Bookmark it   |   submit to dig digg.com Digg it   |   slashdot Slashdot it   |   technorati See who links to it

Comments:

Post a Comment:
  • HTML Syntax: Allowed

This work is licensed under a Creative Commons License.
Copyright 2002-2007, David M Johnson (dave.johnson at rollerweblogger.org)

This is a personal weblog, I do not speak for my employer.