Oran Agra

i see there was a combination of both usleep and yield. @alonre24 do you remember if that was just an attempt to be conservative or did you get any severe...

ok, in our case we have `ctx->next_yield_time = now + 1000000 / server.hz;`, so i don't think that's we have that problem of calling sleep too often.

what do you mean? that both `sched_yield` and `usleep(0)` aren't able to let the main thread grab the mutex?

ok, then merge away! see if the top comment needs any refresh.

first, just to set the right background, these tips are limited. for many commands they're able to reduce the need of the client library or proxy to maintain an explicit...

i'm sorry, i haven't been following this closely. can you please post a short summary of the different approaches and conclusions? we knew (and was willing) to accept some small...

Hi, I briefly reviewed the description above and i think it makes sense. I don't think any interface changes are needed, and i'd even argue that i'm not sure that...

The background is that `alsoPropagate` only worked in the context of `call` so when used in an blocked command (when it gets unblocked), it would have been ignored. IIRC this...

@mohoch1 please share your config, specifically `stream-node-max-entries` and `stream-node-max-bytes`. also, maybe can share `XINFO STREAM ` on that key when it has very few entries and holds huge amount of...

activedefrag can fix problems with `allocator_frag_bytes`, and some cases of high RSS, but in this case it's in `used_memory`, so it's either a leak, or some inefficiency in the stream...