Binbin
I am merging this since #885 is merged, see top comment for more details
> I have seen many instances where number_of_cached_scripts reaches the million level, and used_memory_scripts_eval consumes tens of gigabytes of memory, lol. When a feature is unrestricted, it is prone to...
> I would be more inclined to add a config here so that managed valkey providers have an operational config they can change but the default doesn't change. sound good...
i see #837 does not have this change, do we still need it? @naglera
this is a known issue, https://github.com/redis/redis/issues/11671. we should be able to have a configuration item to limit these such loops.
@madolson i see you marked this, what do we want to do here? Adding a new configuration item that limit the loop, default value is LONG_MAX? I remember discussing this...
ok, the test failed because the old restore use `lazyfree_lazy_server_del` to delete the expired key (not the lazy expire) i am going to leave store alone.
closing since #837 had this change and cover it
lets do it in 8.0, i think we should configure the ideal configuration items for users. btw, i want to change latency-monitor-threshold to default 10ms, just like the slowlog's default...
the current default latency-monitor-threshold is 0 (disable). I see you guys discussed this in here https://github.com/valkey-io/valkey/issues/653#issuecomment-2175590857 the memory one, yean, maybe, or a latency-history-max-len similar to slowlog-max-len? the latency i...