[
https://issues.apache.org/jira/browse/LUCENE-6239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14316123#comment-14316123
]
Uwe Schindler commented on LUCENE-6239:
---------------------------------------
There is one issue: The reference size. If you have an Object[] array, the
compressed/uncompressed OPs difference is huge. I just checked the code with
eclipse we still have that around.
In any case, Unsafe is not used here to modify anything so there is nothing
that can crush, we dont write bytes to non-aligned positions like Netty does
and fails on Sparc. We just call some methods to *retrieve* some values from
the JVM internal - there is no risk (it just mail fail to get the value). I
discussed that already with the JVM guys 2 weeks ago: We are perfectly safe
here, so I don't understand why you suddenly want to remove that code which has
no risk to actually break the JVM? As said, those per-JVM "constants" are hard
to get otherwise.
> Remove RAMUsageEstimator Unsafe calls
> -------------------------------------
>
> Key: LUCENE-6239
> URL: https://issues.apache.org/jira/browse/LUCENE-6239
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
>
> This is unnecessary risk. We should remove this stuff, it is not needed here.
> We are a search engine, not a ram calculator.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
