LevelDB源碼分析之十五:table cache
閱讀本博客可參考:
LevelDB源碼分析之十一:cache
LevelDB源碼分析之十二:block
LevelDB源碼分析之十三:table
由上面這三篇博客可知,LevelDB的Cache分為兩種,分別是table cache和block cache。block是table文件內(nèi)組織數(shù)據(jù)的單位,也是從持久化存儲中讀取和寫入的單位。
block cache是緩存的block數(shù)據(jù)。table cache緩存的是table的索引數(shù)據(jù),因此通過table cache可以遍歷DB所有.sst文件,類似于文件系統(tǒng)中對inode的緩存。
在LevelDB源碼分析之十三:table中用到了block_cache,它實(shí)際上就是一個(gè)NewLRUCache對象,并沒有像table_cache一樣,專門用一個(gè)類TableCache來管理NewLRUCache對象。
下面來簡單分析TableCache。
struct?TableAndFile?{ ??RandomAccessFile*?file; ??Table*?table; }; static?void?DeleteEntry(const?Slice&?key,?void*?value)?{ ??TableAndFile*?tf?=?reinterpret_cast(value); ??delete?tf->table; ??delete?tf->file; ??delete?tf; } static?void?UnrefEntry(void*?arg1,?void*?arg2)?{ ??Cache*?cache?=?reinterpret_cast(arg1); ??Cache::Handle*?h?=?reinterpret_cast(arg2); ??cache->Release(h); } //?從構(gòu)造函數(shù)中可以看出TableCache內(nèi)部管理的是LRUCache對象 TableCache::TableCache(const?std::string&?dbname, ???????????????????????const?Options*?options, ???????????????????????int?entries) ????:?env_(options->env), ??????dbname_(dbname), ??????options_(options), ??????cache_(NewLRUCache(entries))?{ } TableCache::~TableCache()?{ ??delete?cache_; } //?參數(shù)file_number是文件編號,file_size是文件大小 //?參數(shù)*tableptr指向Table對象,當(dāng)然必須先判斷tableptr是不是NULL //?返回某個(gè).sst文件對應(yīng)的Table對象的迭代器 Iterator*?TableCache::NewIterator(const?ReadOptions&?options, ??????????????????????????????????uint64_t?file_number, ??????????????????????????????????uint64_t?file_size, ??????????????????????????????????Table**?tableptr)?{ ??if?(tableptr?!=?NULL)?{ ????*tableptr?=?NULL; ??} ??//?將file_number轉(zhuǎn)換為key ??char?buf[sizeof(file_number)]; ??EncodeFixed64(buf,?file_number); ??Slice?key(buf,?sizeof(buf)); ??//?根據(jù)key查找指定的文件 ??Cache::Handle*?handle?=?cache_->Lookup(key); ??//?如果指定文件不存在,打開文件并添加至緩存 ??if?(handle?==?NULL)?{ ????//?返回新的.sst文件的路徑 ????std::string?fname?=?TableFileName(dbname_,?file_number); ????RandomAccessFile*?file?=?NULL; ????Table*?table?=?NULL; ????Status?s?=?env_->NewRandomAccessFile(fname,?&file); ????if?(s.ok())?{ ??????//?將.sst文件映射到table,Table類用于解析.sst文件 ??????s?=?Table::Open(*options_,?file,?file_size,?&table); ????} ????if?(!s.ok())?{ ??????assert(table?==?NULL); ??????delete?file; ??????//?We?do?not?cache?error?results?so?that?if?the?error?is?transient, ??????//?or?somebody?repairs?the?file,?we?recover?automatically. ??????return?NewErrorIterator(s); ????} ????TableAndFile*?tf?=?new?TableAndFile; ????tf->file?=?file; ????tf->table?=?table; ????//?將tf插入到LRUCache中,占據(jù)一個(gè)大小的緩存,DeleteEntry是刪除結(jié)點(diǎn)的回調(diào)函數(shù) ????handle?=?cache_->Insert(key,?tf,?1,?&DeleteEntry); ??} ??//?cache_->Value(handle)用于返回handle結(jié)點(diǎn)的value ??Table*?table?=?reinterpret_cast(cache_->Value(handle))->table; ??Iterator*?result?=?table->NewIterator(options); ??result->RegisterCleanup(&UnrefEntry,?cache_,?handle); ??if?(tableptr?!=?NULL)?{ ????*tableptr?=?table; ??} ??return?result; } //?Evict含義為”驅(qū)逐“,當(dāng)Compaction時(shí),過期的文件將會被移除,此時(shí)調(diào)用Evict從移除該文件緩存。 void?TableCache::Evict(uint64_t?file_number)?{ ??char?buf[sizeof(file_number)]; ??EncodeFixed64(buf,?file_number); ??//?從LRUCache中刪除對應(yīng)的key結(jié)點(diǎn),不過此時(shí)該結(jié)點(diǎn)內(nèi)容為TableAndFile ??cache_->Erase(Slice(buf,?sizeof(buf))); }