Searched refs:L1 (Results 1 – 4 of 4) sorted by relevance
14 …ed. Files at L0 or L1 may be locked due to involvement in pending L0->L1 or L1->L2 compactions. We…16 …e count in L0 and can be scheduled even when L1 files are locked, unlike L0->L1. We also changed t…18 ### Old L0->L1 Picking Logic24 This compaction pulls in every L0 and L1 file. This happens regardless of which L0 file is initiall…26 …ss uniformly in the key-range. For example, a database may look like this during L0->L1 compaction:32 …L1 prevent us from parallelizing compactions. When locked files block L0->L1 compaction, there is …40 …L1->L2 compaction started first. Now L0->L1 is prevented by the locked L1 file. In this case, we c…46 ### New L0->L1 Picking Logic48 …L1 picking algorithm chose the largest L0 file for compaction. This didn't fit well with L0->L0 co…50 So, we changed the L0->L1 picking algorithm to start from the oldest file and expand towards newer …[all …]
12 As an example, a user can tune the DB as following: use level-based compaction, with L1 - L4 sizes …
185 of the L1+ levels. However, moving the iterator forwards or backwards is simply
4588 auto& L1 = sorted_runs[i].back(); in DoDeterministicCompact() local4589 L1.erase(L1.begin(), L1.begin() + L1.size() / 3); in DoDeterministicCompact()