[
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.patch
Updated and improved patch, for Solr 6.6.0
Adding unit tests for the SizeComponent.
Adding a new parameter, 'sizeUnit', to address @Shawn Heisey 's comment.
If parameter 'sizeUnit' is present, values will be output as 'double',
according to the chosen size unit.
Value of 'estimated-num-docs' remains a 'long'.
Default behavior, if 'sizeUnit' is present is the human-readable format, for
back-compatibility.
Example:
{noformat}
q=*:*&size=true&sizeUnit=GB&rows=0&wt=xml
{noformat}
{noformat}
<?xml version="1.0" encoding="UTF-8"?>
<response>
<lst name="responseHeader">
<int name="status">0</int>
<int name="QTime">0</int>
<lst name="params">
<str name="q">*:*</str>
<str name="size">true</str>
<str name="sizeUnit">GB</str>
<str name="rows">0</str>
<str name="wt">xml</str>
</lst>
</lst>
<result name="response" numFound="6" start="0">
</result>
<lst name="size">
<double name="total-disk-size">2.2901222109794617E-6</double>
<double name="total-lucene-RAM">0.03125092852860689</double>
<double name="total-solr-RAM">0.03147673141211271</double>
<long name="estimated-num-docs">6</long>
<double name="estimated-doc-size">3.809109330177307E-7</double>
<lst name="solr-details">
<double name="filterCache">9.894371032714844E-6</double>
<double name="queryResultCache">2.13623046875E-4</double>
<double name="documentCache">2.2854655981063843E-6</double>
<double name="luceneRam">0.03125092852860689</double>
</lst>
</lst>
</response>
{noformat}
GB is a bit much for a unit test sample size, but you get the idea ;)
> 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, SOLR-8393.patch, SOLR-8393.patch,
> SOLR-8393.patch, SOLR-8393.patch, SOLR-8393.patch, 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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
