Discussing Multi-tenant Indexing and Typesense Clusters
TLDR Semyon enquired about search and indexing performance for multi-tenant indexing. Virginio suggested using Typesense cloud, but Semyon noted the cost difference against bare metal instances. Jason proposed vertical scaling before multi-cluster setup.
Jul 11, 2023 (3 months ago)
• It is quite pricey relative to the other options which are in my opinion quite accessible even though lots of cloud brainwashed people may argue with this statement. I am talking about renting bare metal instance. For example, 64 Gb of RAM on typesense cloud will amount to 1000$ for the simplest, no high availability setup. In contrast I can rent the same hardware for 40$ from Hetzner and get typesense up and running in 20 minutes. Just saying…
Within a single cluster, a good way to shard is to split the data into multiple collections when it reaches say 10s of millions of records and you notice slowdowns for the types of search queries you’re doing (different search params consume different amount of CPU cycles)
Indexed 2786 threads (79% resolved)
Switching from Elastic to Typesense on k8s Cluster
Nicolo needed to know capabilities and features of Typesense. Jason and William provided explanations and shared experiences using it along with documentation links. Nicolo appreciated the insights.
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.