[
https://issues.apache.org/jira/browse/GEODE-9304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17385706#comment-17385706
]
ASF subversion and git services commented on GEODE-9304:
--------------------------------------------------------
Commit d615470200f23999d7cab28582984663d8c42d74 in geode's branch
refs/heads/develop from Donal Evans
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d615470 ]
GEODE-9304: Make RedisSortedSet measurement of bytes in use accurate (#6699)
- Add accurate size calulation to RedisSortedSet
- Make OrderSatisticsSet implement Sizeable
- Add size tracking to OrderStatisticsTree
- Modify how SizeableObject2ObjectOpenCustomHashMapWithCursor
calculates the size of elements to support elements implementing
Siazeable
- Make AbstractOrderedSetEntry implement Sizeable
- Add size calculation to OrderedSetEntry
- Introduce SizeableObjectSizer to efficiently get size in bytes of objects
implementing Sizeable
- Use SizeableObjectSizer internally in
SizeableObject2ObjectOpenCustomHashMapWithCursor and
SizeableObjectOpenCustomHashSet
- Use Double comparison rather than byte array representing double
comparison when both are available
- Add unit tests for all new behaviour
- Add memory overhead integration and acceptance tests for sorted sets
Authored-by: Donal Evans <[email protected]>
> Make RedisSortedSet's measurement of byes in use more accurate
> --------------------------------------------------------------
>
> Key: GEODE-9304
> URL: https://issues.apache.org/jira/browse/GEODE-9304
> Project: Geode
> Issue Type: Bug
> Components: redis
> Affects Versions: 1.15.0
> Reporter: Ray Ingles
> Assignee: Donal Evans
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> The current calculation of bytes in use by RedisSortedSet is inaccurate, and
> needs to be improved. Once a strategy for size calculation for classes using
> Object2ObjectCustomHash and OrderStatisticsTree has been decided, it should
> be implemented for this data type.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
