Set Recycler DEFAULT_INITIAL_MAX_CAPACITY to a more sane value
Motivation: We used a very high number for DEFAULT_INITIAL_MAX_CAPACITY (over 200k) which is not very relastic and my lead to very surprising memory usage if allocations happen in bursts. Modifications: Use a more sane default value of 32k Result: Less possible memory usage by default
This commit is contained in:
parent
dc6c6d956a
commit
445a547265
@ -49,8 +49,7 @@ public abstract class Recycler<T> {
|
|||||||
};
|
};
|
||||||
private static final AtomicInteger ID_GENERATOR = new AtomicInteger(Integer.MIN_VALUE);
|
private static final AtomicInteger ID_GENERATOR = new AtomicInteger(Integer.MIN_VALUE);
|
||||||
private static final int OWN_THREAD_ID = ID_GENERATOR.getAndIncrement();
|
private static final int OWN_THREAD_ID = ID_GENERATOR.getAndIncrement();
|
||||||
// TODO: Some arbitrary large number - should adjust as we get more production experience.
|
private static final int DEFAULT_INITIAL_MAX_CAPACITY = 32768; // Use 32k instances as default max capacity.
|
||||||
private static final int DEFAULT_INITIAL_MAX_CAPACITY = 262144;
|
|
||||||
|
|
||||||
private static final int DEFAULT_MAX_CAPACITY;
|
private static final int DEFAULT_MAX_CAPACITY;
|
||||||
private static final int INITIAL_CAPACITY;
|
private static final int INITIAL_CAPACITY;
|
||||||
|
Loading…
Reference in New Issue
Block a user