Had always wanted to read the Redis source code. But every time I read it, I don't read it. The main is not insist on reading every day. Look every few days. Forget the previous process. More and more do not want to see. It's a sore egg. This is still going to be read out. Planning this period of time is the source of time. are probably using a code flowchart to record what they see. So it is clear to comb. Still have to think oneself see source a bit of problem. Always take a line to see the next line. Often tangled why this value defaults to 5, here is not to be divided by 18 and so on .... I find it unnecessary. Look at the overall framework first. Understand the author's thoughts. Then look at the general flow. The last is to see the concrete details of the implementation. So see the concrete implementation of the later time will be enlightened.
Many notes are pasted into a Youdao notebook. To slowly comb it out. But most of them are pasted and copied. Not much of their own stuff. Sure enough, it's too little to absorb. The input is also small. These are all written in a blog, can be very simple, slowly. Output what you have learned. Only output. To understand faster and understand deeper.
Let's not talk nonsense. Redis's source code parsing article has been a lot. I will not paste the copy. The main is to comb the process of their own see.
Look at the picture, first comb the Simple network part
Redis Network Flowchart < one >