You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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
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.
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?
The text was updated successfully, but these errors were encountered: