You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current implementation starts using paged arrays when the size of the array is
greater than the size of a page. This means that if an array has a length of
${page_size}+1, it will use two pages, wasting about half of the memory.
I think this behavior should be symetric when the size is less than the page
size but higher than half of the page size. This means that we would start
reusing memory at ${page_size}/2 instead of ${page_size}.
The text was updated successfully, but these errors were encountered:
Makes sense to me though it might be worth running performance numbers on it. It might be that you should kick in even earlier. I don't have any ideas on how to measure the performance of such a change though.
jpountz
added a commit
to jpountz/elasticsearch
that referenced
this issue
Feb 28, 2014
I thought about making it kick in earlier but then I would be afraid of wasting too much memory. However, since we are wasting 50% of space in the worst case anyway, I thought it would be useful to take advantage of it to reuse pages more agressively.
Current implementation starts using paged arrays when the size of the array is
greater than the size of a page. This means that if an array has a length of
${page_size}+1, it will use two pages, wasting about half of the memory.
I think this behavior should be symetric when the size is less than the page
size but higher than half of the page size. This means that we would start
reusing memory at ${page_size}/2 instead of ${page_size}.
The text was updated successfully, but these errors were encountered: