Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have rasters in my program of approximately 1500×500 pixels. Each pixel is represented with a float. I believe that means that 1500x500x4(bytes) = 3 million bytes or 3mb. They can be bigger than this. Does the Java Garbage Collector treat big objects differently than smaller ones? Do they skip into a higher generation automatically?
Larger objects can be placed straight into tenured space. The size of the individual objects is what matters e.g.
float[1500][1500]is 1500 objects which are 1500*4 (plus overhead) each.http://blog.dynatrace.com/2011/05/11/how-garbage-collection-differs-in-the-three-big-jvms/
This suggest JRockit does place large objects into tenured space but doesn’t say anything about HotSpot.
This suggests large objects have to be larger than the young generation space to go directly into tenured space.
https://blogs.oracle.com/jonthecollector/entry/size_matters