AWS Typesense Cloud Performance Troubles
TLDR Todd experienced latency issues with Typesense Cloud performance on AWS. Jason suggested testing the same request via ab
and checking the average response times to help diagnose the problem.
Aug 26, 2022 (14 months ago)
Todd
07:16 PMSo I’ve included a segment of our trace that basically is just a typesense query (1.2 seconds). However, when I look in Typesense cloud at the max search latency, I see a much, much lower value (255 ms). I should mention we run a second search immediately afterwards, and it doesn’t have this discrepency at all (259 ms).
We’ve made sure that both our AWS region and our Typesense regions are equivalent (Oregon), but we’re still seeing roughly 1000ms of delay on our first search.
Basically, is there anything we can change about our configuration to reduce this. Can we give the Typesense cloud access to our VPC and use internal URLs, or anything like that? Is there more information I can provide? Thank you
Jason
07:21 PMJason
07:22 PMJason
07:22 PMab
from a server running in Oregon to Typesense Cloud, and post the output here?Jason
07:22 PMTodd
07:27 PMTodd
09:46 PMAug 28, 2022 (14 months ago)
Jason
06:40 PMJason
06:41 PMTypesense
Indexed 2776 threads (79% resolved)
Similar Threads
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.
Troubleshooting Write Timeouts in Typesense with Large CSVs
Agustin had issues with Typesense getting write timeouts while loading large CSV files. Kishore Nallan suggested chunking data or converting to JSONL before loading. Through troubleshooting, they identified a possible network problem at AWS and found a workaround.
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.
Stability Issues with Self-Hosted Typesense Server on AWS ECS
Ryan reports stability issues with a self-hosted typesense server, whilst Jason suggests various potential factors to consider, including configuration, CPU allocation, modifying the healthcheck, and testing on EC2 instances. However, no definitive solution is reached.
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.