On the range of Integer cached in JVM

Question

1.00/5 (1 vote)

See more:

Recently,I found a problem that why JVM caches the values from -128~127 , and I just found the method IntegerCache() and valueOf() says the rules but what is the reason why it is from -128~127 ?

Posted 21-Aug-12 4:34am

mqslll

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Nagy Vilmos · Answer 1 · 2012-08-21T06:53:00

Solution 1

Simply put, these numbers are the most common ones required and the cost/reward of caching 256 instances is worth while.

Posted 21-Aug-12 6:53am

Nagy Vilmos

Comments

mqslll 22-Aug-12 11:00am

And this is the reason ? And this is the JVM character , just caches 256 instances?

Nagy Vilmos 22-Aug-12 11:16am

Probably only need the first 50, but it doesn't cost much in resources so 256 is as good a choice as any other seeing as it is a single byte.