[
https://issues.apache.org/jira/browse/LUCENE-5197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757009#comment-13757009
]
Robert Muir commented on LUCENE-5197:
-------------------------------------
{quote}
What you're doing is actually a skewed view – it measures certain fields
selectively.
{quote}
And from a big O perspective, this might be just fine.
The way i see it, this would be a way to see how much RAM the lucene segment
needs for someone's content.
Things like the terms index and docvalues fields grow according to the content
in different ways: e.g. how large/how many terms you have, how they share
prefixes, how many documents you have, and so on.
The "skew" is just boring constants pulled out of the equation, even if its 2KB
or so, its not interesting at all since its just a constant cost independent of
the content.
> 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, 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]
