Discussions on Typesense's Caching Implementation
TLDR Narayan inquired about typesense's caching implementation; Kishore Nallan clarified results are cached locally by each node.
1
Oct 04, 2023 (2 months ago)
Narayan
03:38 PMuse_cache as described here) a distributed cache in a multi-node typesense setup? Or are query results only cached by the node that served it?
Kishore Nallan
03:48 PM1
Typesense
Indexed 3015 threads (79% resolved)
Similar Threads
Debugging High CPU Usage in Typesense Server
Zsolti was facing high CPU usage in Typesense server in PHP. Mihai suggested using CloudFlare, while Harrison recommended a database for fetching all documents. Kishore Nallan provided information about cache limits and potential improvements.
Improving Documentation for 'cacheSearchResultsForSeconds' Function
Edson suggested that 'cacheSearchResultsForSeconds' function should be included in official documentation. CaptainCodeman shared insights on using caching mechanisms for improving performance. Jason agreed and provided useful details about client-side and server-side caching options in Typesense.
Debugging Search Issue with Typesense Server Caching
Jameshwart reported experiencing caching issues with typesense server, despite the server's default setting of not caching. Through troubleshooting steps with Kishore Nallan, they were able to confirm an issue with the Typesense Javascript client and resolved it by adding `cacheSearchResultsForSeconds: 0` after `apiKey` in the initialisation. Laura also participated in discussion, learning about server and client level caching.