Getting started with Redis to high availability (v)-Single thread

One, single thread why so fast

1) Most requests are purely memory-operated (very fast)
2) Single threaded to avoid unnecessary context switching and competitive conditions
3) non-blocking IO
The internal implementation adopts epoll, and adopts the simple event framework which is implemented by epoll+ itself. Epoll read, write, close, connect to events, and then take advantage of the Epoll multiplexing feature, never waste a little time on Io.

Reference: A word about Epoll

Second, single-threaded need to pay attention to the point

1) run only one command at a time

2) reject the long (slow) command

3) is not a single thread, do some operations (below), there are independent threads to do

FYSNC File Descriptor

FYSNC File Descriptor

Getting started with Redis to high availability (v)-Single thread