denoland / denoland/deploy_feedback

[KV Feedback]: KV database size is growing uncontrollably

Open
#910 0 comments 0 reactions 0 assignees View on GitHub
kv
Dominant language
No language data
Stars
79
Forks
5
PR merge metrics
No merged PRs in 30d

Description

### 🔍

- [x] Did you search for existing issues?

### Type of feedback

Bug report

### Description

I am using KV on Deno Deploy classic. I am storing 4 integers in KV which are updated every couple of minutes via a cron job. My current db size is:
Estimated Size: 132 MiB

I assume this is caused because of point-in-time recovery. So database store not only the last value but every value that is set, which could happen every minute in my case.

How could I reduce the db size? If my assumption above is true, is it possible to remove older values after some time? like no point-in-time recovery after a month.

### Steps to reproduce (if applicable)

_No response_

### Expected behavior (if applicable)

_No response_

### Possible solution (if applicable)

_No response_

### Additional context

_No response_

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.