Why Integer class caching values in the range -128 to 127?

by

Just wondering, why between -128 and 127?

A larger range of integers may be cached, but at least those between -128 and 127 must be cached because it is mandated by the Java Language Specification (emphasis mine):

If the value p being boxed is true, false, a byte, or a char in the range \u0000 to \u007f, or an int or short number between -128 and 127 (inclusive), then let r1 and r2 be the results of any two boxing conversions of p. It is always the case that r1 == r2.

The rationale for this requirement is explained in the same paragraph:

Ideally, boxing a given primitive value p, would always yield an identical reference. In practice, this may not be feasible using existing implementation techniques. The rules above are a pragmatic compromise. The final clause above requires that certain common values always be boxed into indistinguishable objects. […]

This ensures that in most common cases, the behavior will be the desired one, without imposing an undue performance penalty, especially on small devices. Less memory-limited implementations might, for example, cache all char and short values, as well as int and long values in the range of -32K to +32K.

How can I cache other values outside of this range.?

You can use the -XX:AutoBoxCacheMax JVM option, which is not really documented in the list of available Hotspot JVM Options. However it is mentioned in the comments inside the Integer class around line 590:

The size of the cache may be controlled by the -XX:AutoBoxCacheMax=<size> option.

Note that this is implementation specific and may or may not be available on other JVMs.

More Related Contents:

  1. Integer wrapper objects share the same instances only within the value 127? [duplicate]
  2. Java time-based map/cache with expiring keys [closed]
  3. Can Retrofit with OKHttp use cache data when offline
  4. Is method reference caching a good idea in Java 8?
  5. How would you implement an LRU cache in Java?
  6. Easy, simple to use LRU cache in java
  7. Spring Cache @Cacheable – not working while calling from another method of the same bean
  8. Lightweight Java Object cache API [closed]
  9. Android – Bitmap cache takes a lot of memory
  10. Maven docker cache dependencies
  11. Why doesn’t the JVM cache JIT compiled code?
  12. How to Cache InputStream for Multiple Use
  13. Looking for simple Java in-memory cache [closed]
  14. When and how to use hibernate second level cache?
  15. In JNI, how do I cache the class, methodID, and fieldIDs per IBM’s performance recommendations?
  16. alternative to memcached that can persist to disk
  17. Why are immutable objects in hashmaps so effective?
  18. caching images served by servlet
  19. is meta http-equiv value cache control is not supported?
  20. Given N number display M*M format [closed]
  21. Java Calculator minus error
  22. Why is using a wild card with a Java import statement bad?
  23. The AsyncTask API is deprecated in Android 11. What are the alternatives?
  24. Retrieve an Image stored as BLOB on a MYSQL DB
  25. Java 7 default locale
  26. Android: Google Maps API – Change position of maps toolbar
  27. Replacing a text in Apache POI XWPF
  28. How to Replace dot (.) in a string in Java
  29. Android display Splash-Screen while loading
  30. Not thread-safe Object publishing

Leave a Comment