Skip to content
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

do not write multi-part upload data to disk #41

Open
gregjhogan opened this issue Dec 18, 2021 · 4 comments
Open

do not write multi-part upload data to disk #41

gregjhogan opened this issue Dec 18, 2021 · 4 comments

Comments

@gregjhogan
Copy link
Contributor

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 gregjhogan changed the title do not write multi-part upload data to /tmp do not write multi-part upload data to disk Dec 18, 2021
@geohot
Copy link
Owner

geohot commented Dec 18, 2021

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

@gregjhogan
Copy link
Contributor Author

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.

@UlisseMini
Copy link

/dev/shm is always a ramdisk on linux

@awskyfall
Copy link

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

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

4 participants