Handling Large Amount of Facet Values
TLDR Dima asked about handling large amounts of facet values. Jason assured that it is fine and suggested setting max_facet_values to a large number.
1
1
Mar 21, 2023 (9 months ago)
Dima
08:43 PM
Jason
09:15 PMDima
09:17 PMfacet_counts, i.e. possible values for a facet, like ingredients here:
Jason
09:18 PMJason
09:18 PMJason
09:20 PMJason
09:20 PMDima
09:28 PMmax_facet_values to a big number and then get a few kb more with each request :thinking_face: My case is similar to “Brands” here, I have a few hundred thousands of documents and each has association with entity. I don’t really need counts itself, only unique values stored in the fieldDima
09:30 PM* + group_by entity + include entity to get all possible values for this field / search trough them? :thinking_face:Jason
09:41 PMJason
09:42 PMThis would be the only way I can think of achieving what you’re trying to do
1
Jason
09:42 PMThis should be fine
Dima
09:47 PM1
Typesense
Indexed 3015 threads (79% resolved)
Similar Threads
Improving System Performance and Typesense Query Efficiency
SamHendley was experiencing performance issues with Typesense's large-scale system testing and proposed several improvements. Both Jason and Kishore Nallan addressed the suggestions and corrected some misconceptions. They provided further clarification and recommended upgrades for better performance.
Discussion on Retrieving Extra Facet Values
Ricardo inquired about retrieving extra facet values beyond the max_facet_values limit. Kishore Nallan suggested a workaround and asked Ricardo to open a GitHub issue for the feature request.
Querying and Updating Facets in Typesense
Hafiz asked about sum/average of records, hourly grouping, and data formatting in Typesense. Kishore Nallan advised on using `facet_by`, grouping methods, and bulk update options. Hafiz was unable to get sum by group but was advised to store records pre-grouped.
Discussions on Typesense, Collections, and Dynamic Fields
Tugay shares plans to use Typesense for their SaaS platform and asks about collection sizes and sharding. Jason clarifies Typesense's capabilities and shares a beta feature. They discuss using unique collections per customer and new improvements. Kishore Nallan and Gabe comment on threading and data protection respectively.
Discussing Server Side Cache Limit for Optimising CPU Usage.
Aljosa expressed difficulty benefiting from their server's cache due to varied queries, and suggested a cache limit increase. Kishore Nallan provided potential solutions and agreed to make the cache limit configurable. After adjusting queries, Aljosa saw improved CPU usage.