-
Notifications
You must be signed in to change notification settings - Fork 357
Open
Description
Anyone having this issue, or is it just me?
I'm noticing that immudb is consuming a significant amount of disk space per transaction.
For example, with only 60,000 transactions, it has already taken up around 85 GB of storage on my org's cloud compute engine SSD. Each val file is taking 512MB of storage.
This seems unusually high. Is there any known explanation or fix for this?
[I'm using immudb as key-value pair storage DB]
Metadata
Metadata
Assignees
Labels
No labels
