05:14:16 GMT <SirFunk_> Are DEL commands in redis blocking?
10:00:07 GMT <badboy_> SirFunk_: blocking in the sense that they will first delete the key, then return a response, yes
10:00:31 GMT <badboy_> there's UNLINK for asynchronous removal in 4.0: https://redis.io/commands/unlink
18:42:59 GMT <kulelu88> how do I create a human-readable backup of a redis .rdp file?
19:07:35 GMT <minus> kulelu88: there's no builtin mechanism for that
19:08:02 GMT <kulelu88> alright, I'll just carry on with the regular .rdp . thanks minimalism
19:08:05 GMT <kulelu88> minus:
22:45:33 GMT <SirFunk_> badboy_: yeah, were stuck on whaveter AWS Elasticache supports, 2.8 or something. Does it seam probible that a client deleting 2000+ keys one at a time, could cause other clients to time out when doing reads?
22:48:02 GMT <badboy_> yes
22:48:23 GMT <badboy_> if those are huge keys
22:48:43 GMT <badboy_> it also has a slight advantage over other clients by already being connected and firing 2000+ commands
22:53:54 GMT <SirFunk_> ok, I think i've fixed the code a bit to not delete as many keys (it's cache invalidation and we were looping over a bunch of related objects and deleting the same key multiple times)
22:54:22 GMT <SirFunk_> I also am havind it batch into delete calls with < 1000 keys per delete call. Hopefully that will help a little
22:54:53 GMT <SirFunk_> Last busy-season we were using memcached for cache and didn't see problems like this. I'm guessing it blocks less on deletes or something
22:58:02 GMT <minus> how about setting expiry on the keys instead of deleting them directly?