[ 
https://issues.apache.org/jira/browse/GEODE-9285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17359475#comment-17359475
 ] 

ASF subversion and git services commented on GEODE-9285:
--------------------------------------------------------

Commit 16c90dff0a0adb19da78d01e2059574eff9e2bc6 in geode's branch 
refs/heads/develop from Donal Evans
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=16c90df ]

GEODE-9285: Implement accurate sizeable for RedisSet (#6531)

 - Extend ObjectOpenCustomHashSet to allow direct access to the current
 capacity of the backing array
 - Calculate the overhead associated with each member added based on its
 length
 - Calculate the overhead associated with resizing the backing set in
 RedisSet
 - Update tests to reflect new behaviour
 - Add tests to allow derivation of member overhead and backing array
 overhead formulae

Authored-by: Donal Evans <doev...@vmware.com>

> make RedisSet's measurement of bytes in use more accurate
> ---------------------------------------------------------
>
>                 Key: GEODE-9285
>                 URL: https://issues.apache.org/jira/browse/GEODE-9285
>             Project: Geode
>          Issue Type: Improvement
>          Components: redis
>    Affects Versions: 1.15.0
>            Reporter: Hale Bales
>            Assignee: Donal Evans
>            Priority: Major
>              Labels: pull-request-available, redis
>             Fix For: 1.15.0
>
>
> RedisSet currently uses constants to help keep track of the size of bytes in 
> use by that RedisSet. 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. In order to 
> test this with mocks, the delta will need to be set to null explicitly after 
> it is applied.
> This relates to: 
> https://github.com/apache/geode/commit/6a0eba25d5ed5cc7146ce6374d39dd12b22745f3



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to