[
https://issues.apache.org/jira/browse/LUCENE-5197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13756885#comment-13756885
]
Dawid Weiss commented on LUCENE-5197:
-------------------------------------
> Also it totally breaks down if it hits certain objects like a ThreadLocal.
That's why I suggested a visitor pattern, you could tune it not to enter such
variables. Also note that if there are lots of objects then the object
representation overhead itself will be significant and will vary depending on
each VM, its settings, etc; a specific snippet of code to estimate each
object's memory use may be faster but it'll be either a nightmare to maintain
or it'll be a very rough approximate.
I think it'd be better to try to make RUE faster/ more flexible. Like Shai
mentioned -- if it's not a performance-critical API then the difference will
not be at all significant.
> 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]
