Performance Impact of Large Filter Parameters
TLDR Andrew asked about the impact of large filter parameters on cluster performance, conversing with Kishore Nallan for insights, though specific examples were requested for further clarification.
Dec 31, 2022 (9 months ago)
Andrew
05:12 AMIm thinking of implementing a feature that would have a massive filter parameter. Like, possibly many thousands of characters long. As i understand it, this should not impact the performance of my cluster compared to say, a simpler query with under one hundred characters worth of a parameter?
Jan 01, 2023 (9 months ago)
Kishore Nallan
01:08 AMJan 02, 2023 (9 months ago)
Andrew
02:38 AMKishore Nallan
02:44 AM
Typesense
Indexed 2764 threads (79% resolved)
Similar Threads
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.
2Issues and Improvements in Typesense with 14 Million Records
Miguel experienced performance issues when using Typesense for large datasets. Jason suggested performance improvements made to Typesense since then and directed them to specific server-side parameters for better handling. Miguel agreed to try again.
2