Dramatic Improvement with Typesense Indexing.
TLDR Tim shares their excitement over the greatly improved indexing speed they experienced with Typesense, and Jason asks about their use of faceted numerical fields and limitations with long strings and nested fields.
1
1
Feb 14, 2023 (8 months ago)
Tim
03:24 PMI’m super happy about this improvement, so thanks to the Typesense team for whatever it was that happened (I know I also made some changes on my end, but there is no way my tweaks made that big of a difference here)!
1
Jason
04:19 PMTim
05:57 PM1
Typesense
Indexed 2779 threads (79% resolved)
Similar Threads
Performance Issues with Typesense Faceting and Nested Fields
Stefan experiences performance issues when faceting against 23 fields in Typesense, especially with nested fields. Kishore Nallan is working on a solution and will follow up on the thread.
Improving Typesense Query Performance
Jonathan queried about slower than expected typesense query performance. Jason and Kishore Nallan offered solutions and explanations. After a series of tests, Jonathan found other queries returned results quickly, indicating the issue was specific to the original query.
Discussing Document Indexing Speeds and Typesense Features
Thomas asks about the speed of indexing and associated factors. The conversation reveals that larger batch sizes and NVMe disk usage can improve speed, but the index size is limited by RAM. Jason shares plans on supporting nested fields, and they explore a solution for products in multiple categories and catalogs.