Pitfalls - performance

suggest change

Java Pitfalls - Performance Issues

Pitfall - String concatenation in a loop does not scale

Pitfall - Using size to test if a collection is empty is inefficient

Pitfall - Using new to create primitive wrapper instances is inefficient

Pitfall - Interning strings so that you can use == is a bad idea

Pitfall - Efficiency concerns with regular expressions

Pitfall - Small reads and writes on unbuffered streams are inefficient

Pitfall - Over-use of primitive wrapper types is inefficient

Pitfall - Iterating a Map's keys can be inefficient

Pitfall - The overheads of creating log messages

Pitfall - Calling new String(String) is inefficient

Pitfall - Calling System.gc is inefficient

Feedback about page:

Feedback:
Optional: your email if you want me to get back to you:



Table Of Contents