[
https://issues.apache.org/jira/browse/SOLR-8393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17836360#comment-17836360
]
David Smiley commented on SOLR-8393:
------------------------------------
What about Solr's metrics API; has that been explored as a solution to the
problem/need? We can consider adding more metrics.
I don't see why a query should return core metrics.
> 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-1.patch, SOLR-8393.patch, SOLR-8393.patch,
> 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
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> 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
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
