[
https://issues.apache.org/jira/browse/LUCENE-5197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756595#comment-13756595
]
Uwe Schindler commented on LUCENE-5197:
---------------------------------------
>From my perspective: Usage of RAMUsageEstimator is to be preferred, everything
>else gets outdated very fast (especially we have no idea about caches like
>FieldCache used). In production RAMDirectory is not used, and things like MMap
>or NIOFSDir have no heap usage and default codec is also not much, so I see no
>reason to don't trust offical RAM usage as reported by RAMUsageEstimator.
The memory usage counting of IndexWriter is way different to what we have on
the IndexReader side. The accounting done on IndexWriter side are much more
under control of the Lucene code and are very fine granular, but stuff like
proposed changes in FixedBitSet are just nonsense to me. RAMUsageEstimator can
estimate FixedBitSet very correct (that's just easy and in my opinion 100%
correct).
> Add a method to SegmentReader to get the current index heap memory size
> -----------------------------------------------------------------------
>
> Key: LUCENE-5197
> URL: https://issues.apache.org/jira/browse/LUCENE-5197
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/codecs, core/index
> Reporter: Areek Zillur
> Attachments: LUCENE-5197.patch
>
>
> It would be useful to at least estimate the index heap size being used by
> Lucene. Ideally a method exposing this information at the SegmentReader level.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
