You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In hummock, we define different compaction policies for different levels of compaction to achieve the goals of eliminating sub_levels, limiting write amplification, and so on. For example:
Tier Compaction
Base Level Compaction
Other Level Compaction
However, different policies have different constraints. In the current implementation, the restriction logic is implemented in separate pickers. This code is not conducive to maintenance and subsequent development. Moreover, when the compaction does not behave as expected, or even falls into a write stop, adjusting the configuration will be a difficult task.
In order to facilitate code iteration and configuration adjustment, this refactor will be divided into two parts.
Uh oh!
There was an error while loading. Please reload this page.
In hummock, we define different compaction policies for different levels of compaction to achieve the goals of eliminating sub_levels, limiting write amplification, and so on. For example:
However, different policies have different constraints. In the current implementation, the restriction logic is implemented in separate pickers. This code is not conducive to maintenance and subsequent development. Moreover, when the compaction does not behave as expected, or even falls into a write stop, adjusting the configuration will be a difficult task.
In order to facilitate code iteration and configuration adjustment, this refactor will be divided into two parts.
2. Make picker limits switchable for easy adjustmentThe text was updated successfully, but these errors were encountered: