Skip to content

Set Recycler DEFAULT_INITIAL_MAX_CAPACITY to a more sane value#5589

Closed
normanmaurer wants to merge 1 commit into
4.1from
recycler_default_limit
Closed

Set Recycler DEFAULT_INITIAL_MAX_CAPACITY to a more sane value#5589
normanmaurer wants to merge 1 commit into
4.1from
recycler_default_limit

Conversation

@normanmaurer
Copy link
Copy Markdown
Member

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

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
@normanmaurer
Copy link
Copy Markdown
Member Author

normanmaurer commented Jul 27, 2016

Cherry-picked into 4.1 (445a547) and 4.0 (9d764fa)

@normanmaurer normanmaurer deleted the recycler_default_limit branch July 27, 2016 06:00
@normanmaurer normanmaurer self-assigned this Jul 27, 2016
@normanmaurer normanmaurer added this to the 4.0.40.Final milestone Jul 27, 2016
@Scottmitch
Copy link
Copy Markdown
Member

lgtm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants