Why aren’t Integers cached in Java?

by

It should be very clear that caching has an unacceptable performance hit — an extra if statement and memory lookup every time you create an Integer. That alone overshadows any other reason and the rest of the agonizing on this thread.

As far as responding “correctly” to ==, the OP is mistaken in his assumption of correctness. Integers DO respond correctly to == by the general Java community’s expectation of correctness and of course by the specification’s definition of correctness. That is, if two references point to the same object, they are ==. If two references point to different objects, they are not == even if they have the same contents. Thus, it should be no surprise that new Integer(5) == new Integer(5) evaluates to false.

The more interesting question is why new Object(); should be required to create a unique instance every time? i. e. why is new Object(); not allowed to cache? The answer is the wait(...) and notify(...) calls. Caching new Object()s would incorrectly cause threads to synchronize with each other when they shouldn’t.

If it were not for that, then Java implementations could totally cache new Object()s with a singleton.

And that should explain why new Integer(5) done 7 times must be required to create 7 unique Integer objects each containing the value 5 (because Integer extends Object).

Secondary, Less Important Stuff: One problem in this otherwise nice scheme results from the autoboxing and autounboxing feature. Without the feature you could not do comparisons such as new Integer(5) == 5. To enable these, Java unboxes the object (and does not box the primitive). Therefore new Integer(5) == 5 is converted to: new Integer(5).intValue() == 5 (and not new Integer(5) == new Integer(5).

One last thing to understand is that autoboxing of n is not done by new Integer(n). It is done internally by a call to Integer.valueOf(n).

If you think you understand and want to test yourself, predict the output of the following program:

public class Foo {
  public static void main (String[] args) {
    System.out.println(Integer.valueOf(5000) == Integer.valueOf(5000));
    System.out.println(Integer.valueOf(5000) == new Integer(5000));
    System.out.println(Integer.valueOf(5000) == 5000);
    System.out.println(new Integer(5000) == Integer.valueOf(5000));
    System.out.println(new Integer(5000) == new Integer(5000));
    System.out.println(new Integer(5000) == 5000);
    System.out.println(5000 == Integer.valueOf(5000));
    System.out.println(5000 == new Integer(5000));
    System.out.println(5000 == 5000);
    System.out.println("=====");
    System.out.println(Integer.valueOf(5) == Integer.valueOf(5));
    System.out.println(Integer.valueOf(5) == new Integer(5));
    System.out.println(Integer.valueOf(5) == 5);
    System.out.println(new Integer(5) == Integer.valueOf(5));
    System.out.println(new Integer(5) == new Integer(5));
    System.out.println(new Integer(5) == 5);
    System.out.println(5 == Integer.valueOf(5));
    System.out.println(5 == new Integer(5));
    System.out.println(5 == 5);
    System.out.println("=====");
    test(5000, 5000);
    test(5, 5);
  }
  public static void test (Integer a, Integer b) {
    System.out.println(a == b);
  }
}

For extra credit, also predict the output if all the == are changed to .equals(...)

Update: Thanks to comment from user @sactiw : “default range of cache is -128 to 127 and java 1.6 onward you can reset the upper value >=127 by passing -XX:AutoBoxCacheMax= from command line”

More Related Contents:

  1. How do I compare strings in Java?
  2. What is the difference between == and equals() in Java?
  3. equals vs Arrays.equals in Java
  4. Weird Integer boxing in Java
  5. What’s wrong with using == to compare floats in Java?
  6. How to convert int[] into List in Java?
  7. Why do people still use primitive types in Java?
  8. Why do we use autoboxing and unboxing in Java?
  9. Returning null as an int permitted with ternary operator but not if statement
  10. Booleans, conditional operators and autoboxing
  11. Java: Array of primitive data types does not autobox
  12. Why does int num = Integer.getInteger(“123”) throw NullPointerException?
  13. NullPointerException through auto-boxing-behavior of Java ternary operator
  14. Java: How to test on array equality?
  15. Is autoboxing possible for the classes I create?
  16. Does Java guarantee that Object.getClass() == Object.getClass()?
  17. What code does the compiler generate for autoboxing?
  18. Comparing boxed Long values 127 and 128
  19. Is it guaranteed that new Integer(i) == i in Java?
  20. Java Arrays.asList on primitive array type produces unexpected List type [duplicate]
  21. String equality vs equality of location
  22. Java autoboxing and ternary operator madness
  23. How do I convert Double[] to double[]?
  24. Java: What’s the difference between autoboxing and casting?
  25. Does autoboxing call valueOf()?
  26. NullPointerException with autoboxing in ternary expression
  27. Why doesn’t autoboxing overrule varargs when using method overloading in Java 7?
  28. Java Modifying Elements in a foreach
  29. java : Understanding Arrays.asList(T…array) method for primitive types
  30. When “” == s is false but “”.equals( s ) is true

Leave a Comment