Skip to content

Only create NEW checkpoint when necessary #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dtikhonov opened this issue Dec 7, 2017 · 0 comments
Open

Only create NEW checkpoint when necessary #2

dtikhonov opened this issue Dec 7, 2017 · 0 comments
Milestone

Comments

@dtikhonov
Copy link

The model wherein a NEW checkpoint is always available is problematic: this means that the table size can never be zero. This is not good: we want the decoder to be able to specify table size zero.

Instead, a NEW checkpoint should be created implicitly whenever required, which is in two cases:

  1. INSERT_ENTRY command is issued
  2. REUSE_ENTRY command is issued

The cost of the newly created NEW checkpoint is added to the table size at that time. This means that the encoder may not be able to create a NEW checkpoint due to table size constraints. (Which is exactly what we want if the decoder advertizes zero table size.)

@litespeedtech litespeedtech added this to the Second Draft milestone Dec 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants