You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Steve Molloy (JIRA)" <ji...@apache.org> on 2015/12/08 21:04:10 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 ]

Steve Molloy updated SOLR-8393:
-------------------------------
    Attachment: SOLR-8393.patch

Patch based on replication's disk size estimate and adapted Luke's index RAM estimates. Solr RAM estimates tentatively derived from excel sheet provided in dev-tools.

> 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
>         Attachments: SOLR-8393.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
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org