[
https://issues.apache.org/jira/browse/SOLR-16549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637657#comment-17637657
]
Jan Høydahl commented on SOLR-16549:
------------------------------------
Hmm, Yonik says
{quote}I don't like that it's a band-aid around the real problem, but it's the
best pseudo-workaround we currently have I guess (it's based on luck... we're
just lowering the likelihood of a different thread hitting the blocked bucket)."
{quote}
So the problem was around locking, and that Lucene would occationally use the
thread for long-running task, causing long pauses in indexing. I cannot see a
reference to any new Jira issue opened to fix the underlying problem, perhaps
now is the time to open that as a sub task?
> Solr core memory usage study
> ----------------------------
>
> Key: SOLR-16549
> URL: https://issues.apache.org/jira/browse/SOLR-16549
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Noble Paul
> Priority: Major
>
> This is a ticket to study and compare memory usage of cores
> The study is performed on the 9.1 branch
> a simple tests reveals the following. The conclusion is that on an average a
> Solr Core consumes ~3MB of memory for an empty index
> {{cores heap usage }}
> {{---------------------- }}
> {{0 36,623,632 }}
> {{10 68,259,704 }}
> {{20 96,774,456 }}
> {{70 240,501,176 }}
> {{120 379,437,928 }}
> {{200 602,049,784 }}
> {{300 904,252,536 }}
> {{400 1,181,341,200 }}
> {{500 1,455,186,296 }}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
