You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Noble Paul (Jira)" <ji...@apache.org> on 2022/11/15 06:59:00 UTC
[jira] [Comment Edited] (SOLR-16549) Solr core memory usage study
[ https://issues.apache.org/jira/browse/SOLR-16549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17634190#comment-17634190 ]
Noble Paul edited comment on SOLR-16549 at 11/15/22 6:58 AM:
-------------------------------------------------------------
I created a single node cluster and started creating collections .
One missing ingredient is that we can't trigger a GC on a node before we actually get the memory used. So, I had to add an {{@EndPoint}} to trigger a GC
was (Author: noble.paul):
I created a single node cluster and started creating collections .
One missing ingredient is that we can't trigger a GC on a node before we actually get the memory used. So, I had to add a small {{@EndPoint}} to trigger a GC
> 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
> a simple tests reveals the following. The conclusion is that on an average a Solr Core consumes ~30MB 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-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org