Geo Load-Balanced Endpoint Causing Slow Performance
TLDR Edward reported slow responses in their geo load-balanced setup. Kishore Nallan suggested eliminating search_time_ms from the test, which revealed that the issue was not with the LB endpoint. The team will work on improving query latency with facets.
Mar 20, 2023 (6 months ago)
1st screenshot is with the ‘nearest_node’ option and the second is just reverting to using the 3 separate node endpoints. There’s a clear performance difference. I suspect this isn’t correct?
Third screenshot may be related in that sometimes the requests fail but it seems to only fail on the load-balanced endpoint.
Kishore Nallan12:19 PM
Kishore Nallan12:22 PM
Kishore Nallan12:23 PM
Kishore Nallan12:26 PM
Kishore Nallan12:27 PM
Kishore Nallan12:28 PM
search_time_msvalue in the responses just to be sure?
Kishore Nallan12:29 PM
search_time_msand actual network latency.
Kishore Nallan12:30 PM
search_time_msand then try running that via both LB and non-LB end-points.
Kishore Nallan12:36 PM
afkjfkjdskjfsdthat won't exist.
Kishore Nallan12:37 PM
Kishore Nallan12:42 PM
Kishore Nallan12:44 PM
Kishore Nallan12:46 PM
Indexed 2779 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.
Resolving Typesense Cloud Cluster Issue with Cron Job
Issei reported a problem with an unhealthy Typesense Cloud cluster. With the particular help of Jason and Kishore Nallan, they discovered that a problematic cron job was responsible. A solution, using a different endpoint for data export, was agreed on and implemented.
Phrase Search Relevancy and Weights Fix
Jan reported an issue with phrase search relevancy using Typesense Instantsearch Adapter. The problem occurred when searching phrases with double quotes. The team identified the issue to be related to weights and implemented a fix, improving the search results.
Network Errors and Duplicate Requests in Typesense
Ethan and Rushil were experiencing more than 300 network errors and duplicate requests from Typesense. After rigorous troubleshooting, Jason identified the issue as an Instantsearch-induced multiple re-rendering and implemented a fix. Multiple requests reduced, but networking errors persisted, suggested to be due to client-side internet connectivity.