Madelyn Olson

@hpatro Sorry for taking so long to circle back on this, the DCO was failing last time and I forgot to ping you to update. I think this is good...

https://github.com/valkey-io/valkey/actions/runs/9768739963

> Yeah, this change invokes the API more frequently. Someone needs to deep dive further to understand how we reach this state. I deep dived it with an AWS engineer...

@asafpamzn @barshaul Can you give feedback on what you guys think about the implementation.

I feel like we learned a very painful lesson from `CLUSTER SHARDS`, which was although something might seem convenient for clients, they might not adopt it and we end up...

@valkey-io/core-team So reading through this again, right now I don't think we should move forward with the proposal since the use case isn't all that clear. For the SCAN use...

I also like the idea. I just haven't really spent enough time thinking about it. Memory management is a big area in Valkey we need to improve.

I agree with \1. For \2, I'm okay with either it being a percent or a fixed amount, but besides that I think having it be something subtracted from maxmemory...

I've heard headroom less often than more descriptive terms like "spare-capacity" or "reserved-memory". I don't feel that strongly across them though. I like including maxmemory, so I guess my vote...

Decision: We're going to wait until after RC1 to decide what to do about this. It sounds like @hwware had some internal use case where this was important related to...