Skip to content

Conversation

@stephentoub
Copy link
Member

We previously set an arbitrary cut-off of 1MB max array size. That was before we would trim arrays in response to memory pressure. This now raises the limit as high as we can while maintaining the current power-of-two-based scheme.

Contributes to #12800
cc: @jkotas, @Maoni0

@ghost
Copy link

ghost commented Jul 14, 2021

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

@davidfowl
Copy link
Member

I have so much reactionary code to change 😂

@stephentoub stephentoub force-pushed the arraypoollength branch 2 times, most recently from 4421144 to 457144d Compare July 14, 2021 03:54
We previously set an arbitrary cut-off of 2MB max array size. That was before we would trim arrays in response to memory pressure.  This now raises the limit as high as we can while maintaining the current power-of-two-based scheme.
@stephentoub
Copy link
Member Author

I have so much reactionary code to change

Just to confirm, not code that will break because of this, but code where you were working around the lack of this and now don't have to, yes?

@stephentoub stephentoub merged commit fa779e8 into dotnet:main Jul 14, 2021
@stephentoub stephentoub deleted the arraypoollength branch July 14, 2021 15:33
@davidfowl
Copy link
Member

Just to confirm, not code that will break because of this, but code where you were working around the lack of this and now don't have to, yes?

Correct.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants