[
https://issues.apache.org/jira/browse/GEODE-9301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17367773#comment-17367773
]
ASF subversion and git services commented on GEODE-9301:
--------------------------------------------------------
Commit 1f25bbcf7b0809cd464ada7250fb3e48defa7e9c in geode's branch
refs/heads/develop from Donal Evans
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=1f25bbc ]
GEODE-9301: Implement accurate sizeable for RedisHash (#6590)
- Extend Object2ObjectOpenCustomHashMap to allow direct access to the
current capacity of the backing arrays
- Use ReflectionSingleObjectSizer to calculate per-element overhead, as
the previous implementation in SizeableObjectOpenCustomHashSet was
effectively just reimplementing it
- Calculate the overhead associated with resizing the backing arrays
- Update tests to reflect the new behaviour
Authored-by: Donal Evans <[email protected]>
> Make RedisHash's measurement of bytes in use more accurate
> ----------------------------------------------------------
>
> Key: GEODE-9301
> URL: https://issues.apache.org/jira/browse/GEODE-9301
> Project: Geode
> Issue Type: Task
> Components: redis
> Reporter: Donal Evans
> Assignee: Donal Evans
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> RedisHash currently uses constants to help keep track of the size of bytes in
> use by that RedisHash. The way that the size increases when members are added
> is not constant, and is affected by resizing. It is possible to get the
> measurement to be exactly accurate, by dynamically calculating the overhead
> based on the current capacity and how many entries there are.
> This relates to:
> [https://github.com/apache/geode/commit/6a0eba25d5ed5cc7146ce6374d39dd12b22745f3]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
