You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Shawn Heisey (Jira)" <ji...@apache.org> on 2022/03/18 01:01:00 UTC
[jira] [Commented] (SOLR-16102) Performance issue with multiple or in fq
[ https://issues.apache.org/jira/browse/SOLR-16102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508493#comment-17508493 ]
Shawn Heisey commented on SOLR-16102:
-------------------------------------
This project does not use Jira as a support portal. This question belongs on the user list, slack channel, or IRC channel. I will be resolving the issue after I write this comment. If you need more help than I am providing here, please utilize one of those avenues. If we determine that there is a problem that needs fixing, then Jira becomes the correct location for a bug report.
Basically what a query like that boils down to is three hundred separate little queries executing at once. Hopefully Lucene is doing them in parallel, but I am not familiar with Lucene internals to that level, so I cannot say whether that is happening.
That's an enormous amount of work going on.
Will most user queries have very unique fq parameters? If so, the filterCache will be mostly useless for these queries. If the same fq is seen once it has executed once, the cache will make the next occurrences happen quickly.
As much as possible, you should break up a large fq into multiple fq params. Multiple fq parameters are ANDed together, which is probably why you're creating a massive fq in the first place.
> Performance issue with multiple or in fq
> ----------------------------------------
>
> Key: SOLR-16102
> URL: https://issues.apache.org/jira/browse/SOLR-16102
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 8.3.1
> Reporter: Kundan
> Priority: Major
>
> I have a requirement where I need to filter results based on multiple conditions, and I'm analyzing 100 rows in one request.
> If we get millions of such requests then Solr slows down performance.
> ||Total Solr Records||Number of fields in the document||Total 'OR' condition in fq||
> |4402842|13|300+|
> *Why we need these many Or conditions in fq:* We need to analyze production from all 300+ categories, out of 700+ categories.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org