12:39:27 GMT <ramSeraph> Hi
12:39:43 GMT <ramSeraph> looking for some info on the scalability of redis sentinels
12:40:13 GMT <ramSeraph> if i had 10 client host.. can i run 10 sentinels one per host
12:40:34 GMT <ramSeraph> would this be a problem with respect to doscovery and consensus?
17:44:01 GMT <xpd> We've had some issues with Redis during load tests where the delay increases pretty heavily on our WooCommerce site, without any significant CPU usage. Currently using phpredis and sock connection. Any obvious things I can check to improve this?
17:45:25 GMT <xpd> https://imgur.com/a/w4xcU
17:47:39 GMT <minus> xpd: tried to benchmark redis itself? redis-benchmark is included with the distribution
17:48:06 GMT <xpd> I'll try that. any specific command there that is helpful?
17:49:35 GMT <minus> it'll benchmark all (by default) redis commands for throughput (but not latency)
17:49:52 GMT <xpd> running it now
17:50:02 GMT <minus> but should give you an indicator whether you have a bigger performance problem
17:50:26 GMT <xpd> https://www.tights.no/redis-benchmark.txt
17:52:06 GMT <minus> looks fine; 164k gets/s and all in <3ms
17:52:14 GMT <xpd> hm
17:52:20 GMT <xpd> so how do I hunt down the latency?
17:52:30 GMT <minus> are you using a pool?
17:53:21 GMT <minus> tho connection pooling shouldn't have anything to do with that since redis-benchmark is a single connection afaik
17:53:52 GMT <xpd> https://www.tights.no/redis-conf.txt
17:56:37 GMT <minus> https://redis.io/topics/latency-monitor this might help
17:57:17 GMT <minus> i've never run redis with high throughput, so i can't provide any experience-based help unfortunately
18:02:57 GMT <xpd> thank you. I'll try the latency monitor and do some more tests tonight :)