You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The whole search took 2.3sec, of which 1.3 sec was this query.
I'm not sure how each param can be tuned but here are some I know: qf - Since we're currently not using any boost fields. All of these can go: https://solr.apache.org/guide/6_6/the-dismax-query-parser.html#TheDisMaxQueryParser-Theqf_QueryFields_Parameter f.*.facet.limit - Since we're only using 6 here, we can condense this down to facet.limit=>6 and that might help. We might need a condenser function or we can set a default and use individual params like this to override.
This COULD allow us to go back to GET solr queries. We currently use POST because the queries are too long. This could also be another point of slow down
I honestly don't know if this will speed anything up, so do a little testing maybe.
Descriptive summary
General catalog searches produce massive solr queries with mostly empty/irrelevant data. See this example of a simple search for
water
:The whole search took 2.3sec, of which 1.3 sec was this query.
I'm not sure how each param can be tuned but here are some I know:
qf
- Since we're currently not using any boost fields. All of these can go: https://solr.apache.org/guide/6_6/the-dismax-query-parser.html#TheDisMaxQueryParser-Theqf_QueryFields_Parameterf.*.facet.limit
- Since we're only using6
here, we can condense this down tofacet.limit=>6
and that might help. We might need a condenser function or we can set a default and use individual params like this to override.This COULD allow us to go back to
GET
solr queries. We currently usePOST
because the queries are too long. This could also be another point of slow downI honestly don't know if this will speed anything up, so do a little testing maybe.
Expected behavior
Extraneous solr params are cleaned up
Related work
#2862 - This may be the correct solution
Accessibility Concerns
The text was updated successfully, but these errors were encountered: