Understanding Cluster Metrics in Typesense
TLDR Sergio requested for more information on Cluster Metrics such as
typesense_memory_metadata_bytes. Jason and Kishore Nallan provided details on the intended use and meaning of these metrics.
Oct 05, 2022 (15 months ago)
typesense_memory_active_bytes(IIRC) for the actual RAM + Swap that typesense is using, and make sure it never exceeds the total system memory
metadata_byteswhere related to collection usage
fragmentation_ratiois not like documented in Redis. Even if apparently you use same logic.
> A fragmentation ratio less than
1.0means that Redis requires more memory than is available on the system and so it has resorted to using swap memory resources.
Oct 06, 2022 (15 months ago)
Kishore Nallan03:34 PM
stats.mappedetc. on this page: https://manpages.ubuntu.com/manpages/jammy/man3/jemalloc.3.html
Fragmentation ratio is defined as memory allocated divided by memory active. It reflects the additional memory wasted during allocations by the allocator (jemalloc).
Indexed 3015 threads (79% resolved)
Memory Leak Issue in Typesense Server v0.21.0
Jim was experiencing a potential memory leak while load testing an API. Jason and Kishore Nallan suggest it may be a known issue in v0.22.0 RC builds which is resolved in later versions. Jim identifies a specific search filter escalating the issue. Kishore Nallan confirms a fix in the 0.22 RC builds.
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.
Issue Resolution and Upgrade Problems in Typesense Version 0.26rc16
Ankit reported an issue with Typesense, which was addressed by Kishore Nallan and Jason. However, Ankit experienced difficulties while trying to upgrade, with the server status showing as "Not ready or lagging" 503. The resolution remains incomplete.
Typesense Server Crash and Counting Issue
Dan reported a server crash and counting issues with Typesense server version 0.26.0.rc1. Jason suggested an upgrade to `0.26.0.rc13` while Kishore Nallan committed to investigate the issue based on a sample dataset from Dan.