SeveralNotesonRedis

WBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWB
WBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWB원래의
2016-06-07 15:29:041174검색

These notes on Redis are based on its beta version. One could see its source code on my GitHub, where I have tidied the original codes in order to make the codes more easily readable with only around 3,000 code lines. 1. Key Data Structure

These notes on Redis are based on its beta version. One could see its source code on my GitHub, where I have tidied the original codes in order to make the codes more easily readable with only around 3,000 code lines.

1. Key Data Structure

Redis is a kind of key value store. So its key data structure is hash resident in main memory. Keys and values in Redis' hash would be serialized into disk when save command is executed. Here values could be strings, lists, and even sets (not implemented in the beta version). The following graph is borrowed from 《Redis 设计与实现》 to show Redis' key data structure, that is hash.

\

2. Event-driven Implementation

When a client connects to Redis, how does Redis know the client"s connection? How does Redis implement some periodic checks, such as saving database after certain number of changes or time, and resizing the hash? In essence, Redis runs in a while loop, where API select() is used to respond to the above situations.

성명:
본 글의 내용은 네티즌들의 자발적인 기여로 작성되었으며, 저작권은 원저작자에게 있습니다. 본 사이트는 이에 상응하는 법적 책임을 지지 않습니다. 표절이나 침해가 의심되는 콘텐츠를 발견한 경우 admin@php.cn으로 문의하세요.