Oran Agra

@madolson i'm sorry, i don't follow your last post. it seems that you're just pointing out something you already explained earlier, so i don't want to have you repeat that,...

This was discussed in a core-team meeting and was conceptually approved (after applying the changes suggested above)

i'm not sure how useful this is. if you work against a local redis that's not busy, the network overhead and time waiting for execution are small, so indeed you...

WOW.. i have a short memory, and i'm also inconsistent with myself :smile:. let's seek a 3rd opinion. @itamarhaber do you think this is useful enough to justify adding another...

I've created another ticket to complement this one: #2512

while this is probably a good cleanup for the messy unit tests we have, i wonder if it worth all the effort and a ton of lines being moved. the...

i run a quick test to see if it was recently broken or not (tested BRPOPLPUSH being blocked). 2.8, 3.0, 3.2, 4.0 are all completely missing the pop notification. 5.0,...

i think it makes sense to fix the behavior. the doc is very explicit about what should happen, and it's also consistent with other events (Like MOVE), where we first...

we discussed this in a core-team meeting and we weren't sure if we want it, and how useful it is. considering we do have the `activerehashing` config, one can argue...

it's true that if you allocate from just one arena, you'll get lower fragmentation compared to allocating from multiple arenas, and true the jemalloc created multiple arenas when there are...