[ 
https://issues.apache.org/jira/browse/SOLR-15714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matthew Sporleder updated SOLR-15714:
-------------------------------------
    Description: 
[https://solr.apache.org/guide/8_8/query-settings-in-solrconfig.html#documentcache]

 

Advice given for sizing the documentCache is "The size for the documentCache 
should always be greater than max_results times the max_concurrent_queries"

Neither max_results nor max_concurrent_queries are solr keywords or settings.  
They are not defined but they are highlighted as if they are keywords.

Is max_results rows= parameter or total matched documents?
Is max_concurrent_queries http threads who might do a /select or something else?

Furthermore the advice to use the *max* of things for sizing a cache seems 
pretty aggressive when *average* might be better, although it's hard to know 
because the current *max* don't mean anything :)

  was:
[https://solr.apache.org/guide/8_8/query-settings-in-solrconfig.html#documentcache]

 

Advice given for sizing the documentCache is "


> guide bug in documentCache recommendations
> ------------------------------------------
>
>                 Key: SOLR-15714
>                 URL: https://issues.apache.org/jira/browse/SOLR-15714
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: documentation
>            Reporter: Matthew Sporleder
>            Priority: Minor
>
> [https://solr.apache.org/guide/8_8/query-settings-in-solrconfig.html#documentcache]
>  
> Advice given for sizing the documentCache is "The size for the documentCache 
> should always be greater than max_results times the max_concurrent_queries"
> Neither max_results nor max_concurrent_queries are solr keywords or settings. 
>  They are not defined but they are highlighted as if they are keywords.
> Is max_results rows= parameter or total matched documents?
> Is max_concurrent_queries http threads who might do a /select or something 
> else?
> Furthermore the advice to use the *max* of things for sizing a cache seems 
> pretty aggressive when *average* might be better, although it's hard to know 
> because the current *max* don't mean anything :)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org

Reply via email to