[
https://issues.apache.org/jira/browse/LUCENE-8862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16865469#comment-16865469
]
Adrien Grand commented on LUCENE-8862:
--------------------------------------
Memory accounting has a cost API-wise. Like queries, I don't think we should
change the Collector API to enable memory accounting. The only collectors I
have in mind that might allocate lots of memory are the ones that are used to
collect matches in a bitset (there is one for facets and another one in Solr if
I'm not mistaken, different impl but similar idea). If this proves to be a
source of memory issues, we can work on solutions that are specific to those,
similarly to how we only added the Accountable interface to TermInSetQuery?
> Collector Level Dynamic Memory Accounting
> -----------------------------------------
>
> Key: LUCENE-8862
> URL: https://issues.apache.org/jira/browse/LUCENE-8862
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Atri Sharma
> Priority: Major
>
> Inspired from LUCENE-8855, I am thinking of adding a new interface which
> tracks dynamic memory used by Collectors. This shall allow users to get an
> accountability as to the memory usage of their Collectors and better plan
> their resource capacity. This shall also allow us to add Collector level
> limits for memory usage, thus allowing users a finer control over their
> resources.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
