Addressing CPU Utilization Spikes in Typesense Cluster
TLDR Jainil approached for causes and solutions to CPU spikes. Jason clarified and suggested sending 1k-5K records per import API call to mitigate issue.
1
Sep 07, 2023 (2 months ago)
Jainil
06:01 PMJainil
06:02 PM
Jason
06:03 PMIf it's search traffic that's causing CPU spikes, you'll see increases in searches per second and/or search latency
Jason
06:05 PMJainil
06:06 PMJainil
06:07 PMJason
06:07 PMJainil
06:07 PMJainil
06:07 PM1
Typesense
Indexed 3011 threads (79% resolved)
Similar Threads
Typesense Import Issue with HTTP Code 503 Error
Tomas faced errors while importing to typesense, including an HTTP code 503. Jason identified the issue as CPU exhaustion and recommended slowing down writes or upgrading to at least 4vCPU.
Typesense Cloud Cluster Issue and Upgrade Recommendations
Viji reported a cluster issue on Typesense Cloud. Jason identified the cause and recommended upgrading to Typesense 0.24.1 for safeguards against RAM usage spikes.
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.
Addressing Typesense Server Issues and Optimization Needs
Robert had an issue with a 'stuck' typesense server. Jason and Kishore Nallan gave advice on handling writes, configuration for high search volumes, and running multiple typesense instances. They also recommended monitoring CPU usage and updating the server version for bug fixes.
Resolving 100% CPU Usage Issue in Self-Hosted Typesense
Hariharan reports high CPU usage during evening hours on their self-hosted Typesense setup. Kishore Nallan suggests checking for external processes and enabling access logging to identify the cause, but the issue remains unresolved.