
Performance
Get flash to fully experience Pearltrees
Optimizing Client-Side Performance
Java performance tuning tips
Java Performance Tuning Java(TM) - see bottom of page Our valued sponsors who help make this site possible FREE Java Performance Troubleshooting Tool from AppDynamics. Download now! New Relic: Try free w/ production profiling and get a free shirt!The Performance of Java's Lists
<a href="http://adserver.adtechus.com/adlink/3.0/5159/425846/0/16/ADTECH;loc=300;key=key1+key2+key3+key4;grp=[group]" target="_blank"><img src="http://adserver.adtechus.com/adserv/3.0/5159/425846/0/16/ADTECH;loc=300;key=key1+key2+key3+key4;grp=[group]" border="0" width="1" height="1"></a> The SDK has several implementations of the ordered collection interface java.util.List . The three best known are Vector, ArrayList, and LinkedList. <a href="http://adserver.adtechus.com/adlink/3.0/5159/425855/0/170/ADTECH;loc=300;key=key1+key2+key3+key4;grp=[group]" target="_blank"><img src="http://adserver.adtechus.com/adserv/3.0/5159/425855/0/170/ADTECH;loc=300;key=key1+key2+key3+key4;grp=[group]" border="0" width="300" height="250"></a> One question that frequently reaches the Java Performance Tuning site asks about the performance differences between these List classes.Last updated Jul 3, 2009. In recent years, test-driven development, or at least the process of employing unit tests, has been touted as one of the best mechanisms for developing high-quality code. The reason for test-driven development, or TDD, gaining such widespread adoption is that tested code typically yields higher quality results than untested code (makes sense, right?) The different between TDD and simply writing test cases is that TDD defines a formal process for when and by whom test cases should be written: TDD states that test cases should be written before code is written and that test cases should be written by the developer writing the code that is to be tested.
Java Reference Guide > Unit Testing: Tips From The Trenches
Last updated Jul 10, 2009. One challenge that we face when writing unit tests is how to test components at a fine-granularity. For example, if you have a web-based application, testing a request as it passes from an action through a business service tier, back to a data access tier, and back out, is a good thing to do, but if the result is incorrect, how do you know where the problem is?

