Slow Performance of Faceted Query with Increased Fields
TLDR John experienced slowdown in faceted queries after increasing to 1000 fields. Upgrading from 0.24.0.rcn21 to 0.24.0 improved performance. The issue was attributed to John using an ARM build on an M1 Mac.



Feb 23, 2023 (7 months ago)
John
04:32 PMBefore: ~100 fields, faceting by 8 fields with
max_facet_values=100
=> ~0.3 secondsAfter: ~1000 fields, faceting by 8 fields with
max_facet_values=100
=> ~1.5 seconds (without faceting ~0.08 seconds)John
04:34 PMJason
05:29 PMFeb 24, 2023 (7 months ago)
John
10:29 AMKishore Nallan
10:32 AMJohn
10:33 AM"search_cutoff": false
so doesn’t seem like itKishore Nallan
10:33 AMKishore Nallan
10:34 AMJohn
10:38 AMJohn
12:24 PMKishore Nallan
12:27 PM
John
12:32 PM0.24.1.rc4
so there’s something special about the 0.24.0
I’m running 😄Kishore Nallan
12:34 PMJohn
12:37 PMFast (search_time_ms=130): found=1102, out_of=5800
Slow (search_time_ms=1361): found=945, out_of=2053
John
12:37 PMJohn
12:39 PMKishore Nallan
12:40 PMKishore Nallan
12:41 PMJohn
12:51 PM

Kishore Nallan
12:51 PMTypesense
Indexed 2764 threads (79% resolved)
Similar Threads
Production Typesense Issue with Unexpected Filter Behavior
Ankit flagged a problem with a specific filter on the production server of Typesense. After several exchanges regarding optimisation and version checks, Kishore Nallan provided latest builds to troubleshoot. The filtering within facets issue persists and potential edge cases are being investigated.


Discussing Search API Limitations and Solutions
Sidharth had problems with search API response limitations and sorting issues. Kishore Nallan suggested multi_search query and provided links for an updated version. After installation, some timeout and performance issues were encountered, partially resolved by adjusting client timeout values.

Slow, High CPU Write Operations After Collection Drop in Typesense
Himank discussed an issue in Typesense where deleting and recreating a collection led to slow write operations and high CPU usage. Kishore Nallan suggested using an alias to avoid this issue. Numerous tests and debugging was conducted as pboros contributed with local testing. Kishore Nallan aimed to start implementing a range delete and full db compaction after deletion to potentially solve the issue.



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.
Improving Search Response Time in Typesense
Ed expressed concerns about higher search response times. Jason identified the high max facet value and average record size factors contributing to the issue. They also discussed options to enhance performance, such as limiting facet values display and upgrading the CPU.
