You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Isabelle Giguere (JIRA)" <ji...@apache.org> on 2018/10/11 15:46:00 UTC
[jira] [Updated] (SOLR-8393) Component for Solr resource usage
planning
[ https://issues.apache.org/jira/browse/SOLR-8393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Isabelle Giguere updated SOLR-8393:
-----------------------------------
Attachment: SOLR-8393_tag_7.5.0.patch
> Component for Solr resource usage planning
> ------------------------------------------
>
> Key: SOLR-8393
> URL: https://issues.apache.org/jira/browse/SOLR-8393
> Project: Solr
> Issue Type: Improvement
> Reporter: Steve Molloy
> Priority: Major
> Attachments: SOLR-8393.patch, SOLR-8393.patch, SOLR-8393.patch, SOLR-8393.patch, SOLR-8393.patch, SOLR-8393.patch, SOLR-8393.patch, SOLR-8393_tag_7.5.0.patch
>
>
> One question that keeps coming back is how much disk and RAM do I need to run Solr. The most common response is that it highly depends on your data. While true, it makes for frustrated users trying to plan their deployments.
> The idea I'm bringing is to create a new component that will attempt to extrapolate resources needed in the future by looking at resources currently used. By adding a parameter for the target number of documents, current resources are adapted by a ratio relative to current number of documents.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org