Skip to content

[Feature]: Dirty memory size triggered CKPT #390

Description

@githubzilla
  • Summary (Provide a general summary of the issue in the Title above):(required)

    • Leverage the statistics of dirty key ratio to trigger the CKPT
    • Base on the dirty key ratio and current memory foot print to calculate the actually dirty memory ratio to the total memory limit
    • If the dirty memory ratio is bigger than 20%, then trigger a checkpoint
    • Remove original checkpoint trigger when memory is full
  • Detailed Description (Provide a detailed description of the change or addition you are proposing):(required)

  • Software version (the version of the software you're running):(required)
    e.g. 0.0.1

  • Possible Implementation(suggest an idea for implementing addition or change)(optional)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

featureAdd new feature

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions