Hey Everyone Can anyone explain to me what exactly healthy-read-lag and healthy-write-lag configuration parameters and how they impact writes and search queries. @Jason Bosco please help me with this, how we can tune these parameters for a high number of writes and a high number of search queries.

Hey there! Let me help clarify these Typesense configuration parameters. The

healthy-read-lag

and

healthy-write-lag

are essentially safety thresholds that Typesense uses to maintain system health and data consistency. Think of them as traffic controllers for your operations. When you set

healthy-read-lag

(default 1000), you're telling Typesense "hey, if reads fall behind by more than this much, start rejecting read queries." This helps avoid serving outdated data to users. Similarly,

healthy-write-lag

(default 500) controls when to start rejecting writes if the system gets too backed up. For high-volume scenarios, you might want to tweak these values higher to give your system more breathing room to handle the load. But there's a trade-off - higher values mean potentially serving slightly older data. It really depends on what's more important for your specific use case: data freshness or handling more operations. Let me know if you want to discuss specific numbers for your setup - it'd help to know more about your hardware and requirements

Thanks, I got the point. I need handling more operations. So I will increase those both parameters to 10k.