-
Notifications
You must be signed in to change notification settings - Fork 157
Redis training plan and learning notes
Warren Zhu edited this page Dec 11, 2017
·
1 revision
Please refer (https://redis.io/documentation)
Topic | Reference | Time spent | Question |
---|---|---|---|
Pipeline | 1 hour | ||
Eviction policy | 1 hour | ||
Partition | 1 hour | ||
Transaction | |||
Persistence | |||
Memory optimization | |||
Publish/Subscribe | |||
Replication | |||
Connection handling | |||
High Availability | |||
Benchmark | |||
Internal | |||
Troubleshooting |
Pipelining is primarily a network optimization. It essentially means the client buffers up a bunch of commands and ships them to the server in one go. The benefit here is saving network round trip time and combining multiple write() or read() system call for every command.