Madelyn Olson

Kicked off a full-run to stress this code a bit more before merging: https://github.com/valkey-io/valkey/actions/workflows/daily.yml

Actual test run I kicked off: https://github.com/valkey-io/valkey/actions/runs/9764931105

@adetunjii https://github.com/valkey-io/valkey/issues/533

@adetunjii btw, if you comment on issues I can assign them to you so it's clearer that someone is working on it.

Overall this seems sane to me. I'm running some extra tests since we had some issues last time on the systems that don't use jemalloc.

@valkey-io/core-team Please vote on the new configuration. Also please comment about if we should change the name from `flushdb` -> `flushall`, since we aren't flushing a single database, so this...

Do you have more of a concrete use case that you are mentioning? I was also originally a fan of using the client output buffer limit to keep the configuration...

Preference from the core discussion was that we preferred no-config since the buffer size is not the client output buffer. There is a general preference that this configuration should be...

> Is there an existing action item or plan to implement RDB size prediction capabilities? If not, would it be possible to create one? Having this functionality would enable us...

@valkey-io/core-team Please vote on this small feature, we can optionally include it in Valkey 8.0 if it's ready for rc2, but not after.