Complex Filtering of Queries Impacting Performance
TLDR SamHendley reported unexpected performance issues after adding new filters to permissions. Kishore Nallan requested a sample dataset to better understand the problem.
Dec 30, 2022 (9 months ago)
• Is there a performance penalty to filtering on
I have recently added some new filtering to support permissions and it has made all of my queries much slower, more so than I would have expected. A simple
infilter on a
stringfacet seems to have basically no impact on performance (in fact faster since I am pruning the returned documents). If I add two more
infilters to the query it has big impact on perf. This first filter is selecting down from
I think I am probably going down the wrong path trying to combine my low cardinality (
Dec 31, 2022 (9 months ago)
Kishore Nallan04:16 AM
Indexed 2776 threads (79% resolved)
Performance Characteristics of Filtering Search Results
Oskar queries the performance difference in filtering search results. Jason clarifies how filters work and provides performance improvement suggestions like increasing vCPUs and sharding the collection. Kishore Nallan explains filter IDs and document ID matching. The thread concludes with discussions on performance tradeoffs in filter implementation.
Performance Issues with Adding Filters to Large Datasets
Cirdes is experiencing slower response times when adding filters to a large dataset. Jason suggests trying a different version and using a different format for filters. They also inquire about the value of the 'found' field and if removing the sort_by field improves performance. SamHendley chimes in with their own similar issues and Kishore Nallan offers to discuss solutions further in DM. krok expresses interest in the discussion. Further tests and optimizations are planned.
Usage and Modification of Dynamic Routes in Typesense Documents
Ethan needed a way to perform exact queries through two fields in Typesense documents. Kishore Nallan demonstrated its possibility using the "filter_by". An issue was resolved via recommending that fields in 'query by' should be a string type.