Badrish Chandramouli

> Huh, `dotnet format` gives me nothing locally 🤔 @TalZaccai?

> We had issues in production due to queued up SETEX when batch storing. This is probably a Redis-specific issue. Garnet should do fine with `SETEX` sent by `StackEchange.Redis` which...

The linked PR https://github.com/microsoft/garnet/pull/369 augments custom stored procedures to support a variable number of parameters (similar to `MSET`) and further uses this to implement `MSETPX` as a custom proc.

> Redis should have done fine with the long queue of SETEX too Redis being single threaded processing on the server side, would have choked on this scenario, even if...

Closing as per provided workarounds, thanks!

@tli2 - any idea about this?

We do have basic RESP3 support in the latest. Would like to know what specific operator is not working correctly.

@mperham - do we have everything we need for Sidekiq to work at this point?

This is a solid idea. You are right that server is a big user of stackalloc. Out of curiosity, did you try adding it and notice tests failing out of...

As discussed offline, closing PR for now as we are not seeing end-to-end perf advantages for cache workloads. We can revisit this setting in the future. Thanks!