In scenarios where large amount of chunks are stored, in this case of large batch expirations or unpinning large amount of chunks, disk usage remains the same.
We need some defragmentation process that shrinks sharky chunk/shard to the smallest size possible.
This could be a cmd a user can run on demand and does need to be tied to the normal bee node operations.
In scenarios where large amount of chunks are stored, in this case of large batch expirations or unpinning large amount of chunks, disk usage remains the same. We need some defragmentation process that shrinks sharky chunk/shard to the smallest size possible. This could be a cmd a user can run on demand and does need to be tied to the normal bee node operations.