Improving Search Time in Typesense
TLDR Vasudev sought for ways to improve server response time in Typesense. Kishore Nallan suggested it might be network latency or Postman's request process. Harrison confirmed that Postman is usually slow.
Oct 05, 2022 (15 months ago)
Kishore Nallan04:52 AM
Kishore Nallan04:53 AM
And it has only 3 records
Kishore Nallan04:55 AM
search_time_msin the response?
Kishore Nallan04:56 AM
Is this api is triggered when we are typing something in UI
Kishore Nallan05:00 AM
"search_time_ms": 0but postman is showing
Kishore Nallan06:06 AM
Kishore Nallan06:08 AM
/collections/:name/documents/:idfor this endpoint there is no such field
Kishore Nallan06:10 AM
Kishore Nallan06:15 AM
Kishore Nallan07:16 AM
Indexed 3011 threads (79% resolved)
Discussing Typesense Search Request Performance
Al experienced longer-than-reported times for Typesense search requests, sparking a detailed examination of json parsing, response times and data transfer. Jason and Kishore Nallan helped solve the issue.
Optimizing Typesense Implementation for Large Collections
Oskar faced performance issues with his document collection in Typesense due to filter additions. Jason suggested trying a newer Typesense build and potentially partitioning the data into country-wise collections. They also discussed reducing network latency with CDN solutions.
Revisiting Typesense for Efficient DB Indexing and Querying
kopach experienced slow indexing and crashes with Typesense. The community suggested to use batch import and check the server's resources. Improvements were made but additional support was needed for special characters and multi-search queries.
Troubleshooting Indexing Duration in Typesense Import
Alan asked about lengthy indexing times for importing documents to Typesense. Jason suggested various potential causes, including network connectivity and system resources. They later identified the problem to be an error in Alan's code.
Typesense Server Bulk Import/Upsert Issue Resolved
Adam was confused about the discrepancy between the successful responses and the actual indexed data while working with a custom WP plugin integrating with Typesense. The issue was a bug related to fetching documents in the wrong order, not a Typesense problem.