00:00:07 GMT <hakunin> minus: hm 10Hz is pretty fast, faster than reasonable polling i'd say
00:00:22 GMT <hakunin> fast=frequent
00:01:15 GMT <minus> redis-cli config get hz
00:02:15 GMT <minus> set it to 100 and be golden?
00:02:24 GMT <hakunin> just realized a problem with this
00:02:31 GMT <hakunin> minus: redis expires 20 random keys
00:02:38 GMT <hakunin> not all keys
00:02:50 GMT <minus> 20 random keys each tick?
00:02:53 GMT <hakunin> yes
00:02:56 GMT <minus> interesting
00:02:59 GMT <hakunin> https://redis.io/commands/expire
00:03:04 GMT <hakunin> in "how redis expires keys"
00:03:55 GMT <hakunin> it's not exactly 20, but it gives no guarantees that all keys will get expired
00:03:55 GMT <minus> it tests 20 keys that have expiry set*
00:04:08 GMT <hakunin> rather removed
00:04:26 GMT <hakunin> some keys might live on for many ticks i presume
03:12:04 GMT <rawburt> Does Redis allow duplicate keys?
03:14:07 GMT <rawburt> Nevermind- clearly an error with my script
14:42:43 GMT <Guest10149> is there any reason not to pipeline all commands, even just groups of two?
14:49:48 GMT <minus> pipelining just means your client doesn't wait for the reply, no reason to not use it if you don't need the result immediately
14:50:10 GMT <minus> though i'm not sure every library supports that
14:50:39 GMT <minus> redis-py has a pipeline functionality but that actually starts a transaction (MULTI/EXEC)