You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi.
I'm new to redis, and currently I am making some tests to see the performance when sending lots of records no a redis sentinel configuration.(1 master with one slave and 3 sentinels wich monitors the master).
The idea is to send 30 000 000 records to a redis db as fast as possible and then to wait for the result to see how many of them crashed or not.
The code I', using is :
In #1854 we switched to a `Thread` here to prevent the pile-up case, however under concurrent load this incurs a 10-11% penalty given backlogs aren't all that uncommon (due to the lock contention case). In .NET 6.0+, let's use the thread pool growth semantics to handle the stall case and use the cheaper `Task.Run()` approach.
Running the benchmarks from #1164 I was experimenting with on lock perf, I noticed a large perf sink in thread creation as a result of lock contention. For that benchmark as an example (high concurrent load) we're talking about a ~93 second -> ~84 second run reduction and similar wins in concurrent load tests.
Hi.
I'm new to redis, and currently I am making some tests to see the performance when sending lots of records no a redis sentinel configuration.(1 master with one slave and 3 sentinels wich monitors the master).
The idea is to send 30 000 000 records to a redis db as fast as possible and then to wait for the result to see how many of them crashed or not.
The code I', using is :
Is there a faster way to send messages and after sending them to wait for the responses ?
The text was updated successfully, but these errors were encountered: