Is your feature request related to a problem? Please describe.
The in-mem cache is used for downloads currently. It is implemented as a write through cache where the download is first added to memory and then is drained to disk asynchronously.
This helps in reducing the turn around time of the request by serving the blobs from memory rather than from disk.
However, the upload path was not touched. This issue aims to consider uploads also using the in-mem cache
Describe the solution you'd like
The upload path is a bit different because we need to make sure we are durable on the storage in memory when we try to upload to bucket.
The download path is more of an availability problem, that's why it was the first candidate to be implemented.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Is your feature request related to a problem? Please describe.
The in-mem cache is used for downloads currently. It is implemented as a write through cache where the download is first added to memory and then is drained to disk asynchronously.
This helps in reducing the turn around time of the request by serving the blobs from memory rather than from disk.
However, the upload path was not touched. This issue aims to consider uploads also using the in-mem cache
Describe the solution you'd like
The upload path is a bit different because we need to make sure we are durable on the storage in memory when we try to upload to bucket.
The download path is more of an availability problem, that's why it was the first candidate to be implemented.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.