[
https://issues.apache.org/jira/browse/DIRECTMEMORY-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211297#comment-13211297
]
Raffaele P. Guidi commented on DIRECTMEMORY-63:
-----------------------------------------------
I agree on the size part, but I think hashes are not guaranteed to be unique -
an object has only one hash but different objects can have the same hash.
Obviously, it's not a common case but it can happen and that's why I think it
should be a configurable behaviour. The tradeoff, of course could be well
worth. Any possible way to mitigate risks of getting the wrong object?
> Investigate removing the need for an on heap map to store keys/pointers.
> ------------------------------------------------------------------------
>
> Key: DIRECTMEMORY-63
> URL: https://issues.apache.org/jira/browse/DIRECTMEMORY-63
> Project: Apache DirectMemory
> Issue Type: Improvement
> Reporter: Michael André Pearce
>
> On performance testing and monitoring jvm heap allocation, it became clear
> that as the off heap elements increased so did the on heap used memory. This
> is because DirectMemory is storing keys and pointers in the heap meaning that
> the cache isn't fully off heap, and on heap memory will increase linearly
> with elements in the cache.
> An idea maybe is to look into using a key's hash for location on a separate
> single off heap buffer to store the main heaps pointers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
