Troubleshooting a High Volume Search Response
TLDR Sophie experienced oversized search responses despite setting a lower limit. Jason suggested checking the results count and limiting the return values in each document, which resolved the issue.
Sep 23, 2023 (2 months ago)
qvalue should work fine with this collection anyway
curl <your search request> | jq '.hits | length'
Indexed 3015 threads (79% resolved)
Optimizing Uploads to Typesense and Dealing with Hits Limit
Masahiro asked how to upload documents to Typesense faster and about their search feature limit_hits. Jason suggested batching documents and debugged the search query. Issue was resolved.
Integrating Semantic Search with Typesense
Krish wants to integrate a semantic search functionality with typesense but struggles with the limitations. Kishore Nallan provides resources, clarifications and workarounds to the raised issues.
Increase Search Result Size and Filter Special Characters
Anton requested pagination beyond 250 hits per page and precise filtering for terms with special characters. Jason suggested multi-search as a workaround and planned to address special character filtering in an upcoming release. A Github issue was created to track this feature request.
Issues 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.
Enhancing Vector Search Performance and Response Time using Multi-Search Feature
Bill faced performance issues with vector search using multi_search feature. Jason and Kishore Nallan suggested running models on a GPU and excluding large fields from the search. Through discussion, it was established that adding more CPUs and enabling server-side caching could enhance performance. The thread concluded with the user reaching a resolution.