- Docs https://redis.io/docs
- Commands list: https://redis.io/commands/
- They have extra courses https://university.redis.com/
To monitor all commands executed on server ¶
1$ redis-cli MONITOR
Client-side caching ¶
one of the modes is to subscribe to key prefix and the server send updates when it receives it.
Bulk loading data ¶
1cat data.txt | redis-cli --pipe
Interesting Quotes ¶
It had a Gopher protocol implementation ¶
Setup seems to need some tweaking from the kernel ¶
as provided here: https://redis.io/docs/manageme…
- Set the Linux kernel overcommit memory setting to 1. Add vm.overcommit_memory = 1 to /etc/sysctl.conf. Then, reboot or run the command sysctl vm.overcommit_memory=1 to activate the setting.
- To ensure the Linux kernel feature Transparent Huge Pages does not impact Redis memory usage and latency, use this command:
echo never > /sys/kernel/mm/transparent_hugepage/enabled
- Same page has many other good tips about deployment on AWS EC2 and what kind of machines to use
Marketing speak ¶
in the Sentinel page I started to smell marketing speak bullshit:
You need at least three Sentinel instances for a robust deployment
What does robust deployment even mean?
As usual the best pages are the pages talking about the internals. such as the events library or string internals. it’s outdated (since 2010) but it speaks true of what the software is and what happens inside it. reminds me of the Varnish architecture document.