[
https://issues.apache.org/jira/browse/SOLR-15714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17436973#comment-17436973
]
Michael Gibney commented on SOLR-15714:
---------------------------------------
The old blog post is interesting, because it suggests that at some point the
"<angle-bracket delimited>" informal value placeholders from the wiki (as cited
in the blog post) may have been converted to {{backtick-delimited}}
placeholders, inadvertently suggesting more formal keywords or variable names.
Perhaps what you really want is neither strictly "average", nor "peak/max", but
some reasonable approximation of "average peak/max" -- afaik out-of-the-box
Solr doesn't support an arbitrary hard limit on max concurrent queries, so
tuning the cache size isn't an exact science, and no matter how high you set
the size, there will be some load threshold at which you'll see performance
degradation :-)
That said, an alternative to reworking this section might just be to convert
the backticks back to angle-brackets. I think people will get the idea, and if
the main problem we're hoping to address is "people digging through
documentation trying to figure out where these formal parameters are", then
angle-brackets might just suffice?
> 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
