minikeyvalue icon indicating copy to clipboard operation
minikeyvalue copied to clipboard

do not write multi-part upload data to disk

Open gregjhogan opened this issue 4 years ago • 4 comments

Writing to /tmp will wear out your OS drive pretty fast pumping hundreds of terabytes into minikeyvalue. Since RAM is good enough for non-multipart uploads, it should be fine for multi-part uploads, too. Maybe we want to suggest using a RAM disk and add expiring partial uploads where the final PUT never happens within some time period?

gregjhogan avatar Dec 18 '21 02:12 gregjhogan

I mean /tmp should be a ramdisk. But I'm supportive of the Go managing these as ram buffers directly.

geohot avatar Dec 18 '21 02:12 geohot

I wasn't sure how complicated buffering in Go would be, but we definitely should add something to expire stale multi-part upload data in Go either way.

gregjhogan avatar Dec 18 '21 05:12 gregjhogan

/dev/shm is always a ramdisk on linux

UlisseMini avatar Apr 30 '22 00:04 UlisseMini

I mean /tmp should be a ramdisk. But I'm supportive of the Go managing these as ram buffers directly.

awskyfall avatar Jul 05 '23 06:07 awskyfall