mirror of
https://github.com/minio/minio.git
synced 2024-12-26 23:25:54 -05:00
49 lines
2.7 KiB
Markdown
49 lines
2.7 KiB
Markdown
# Disk Caching Design [](https://slack.minio.io)
|
|
|
|
This document explains some basic assumptions and design approach, limits of the disk caching feature. If you're looking to get started with disk cache, we suggest you go through the [getting started document](https://github.com/minio/minio/blob/master/docs/disk-caching/README.md) first.
|
|
|
|
## Command-line
|
|
|
|
```
|
|
minio server -h
|
|
...
|
|
...
|
|
CACHE:
|
|
MINIO_CACHE_DRIVES: List of cache drives delimited by ";"
|
|
MINIO_CACHE_EXCLUDE: List of cache exclusion patterns delimited by ";"
|
|
MINIO_CACHE_EXPIRY: Cache expiry duration in days
|
|
...
|
|
...
|
|
|
|
7. Start minio server with edge caching enabled on '/drive1', '/drive2' and '/drive3',
|
|
exclude all objects under 'mybucket', exclude all objects with '.pdf' as extension
|
|
with expiry upto 40 days.
|
|
$ export MINIO_CACHE_DRIVES="/drive1;/drive2;/drive3"
|
|
$ export MINIO_CACHE_EXCLUDE="mybucket/*;*.pdf"
|
|
$ export MINIO_CACHE_EXPIRY=40
|
|
$ minio server /home/shared
|
|
```
|
|
|
|
## Assumptions
|
|
- Disk cache size defaults to 80% of your drive capacity.
|
|
- Disk caching requires [`atime`](http://kerolasa.github.io/filetimes.html) support to be enabled on the cache drive.
|
|
- Expiration of each cached entry takes user provided expiry as a hint, and defaults to 90 days if not provided.
|
|
- Garbage collection sweep of the expired cache entries happens whenever cache usage is > 80% of drive capacity, GC continues until sufficient disk space is reclaimed.
|
|
- An object is only cached when drive has sufficient disk space, upto 100 times the size of the object.
|
|
|
|
## Behavior
|
|
Disk caching caches objects for both **uploaded** and **downloaded** objects i.e
|
|
|
|
- Caches new objects for entries not found in cache while downloading. Otherwise serves from the cache.
|
|
- Caches all successfully uploaded objects. Replaces existing cached entry of the same object if needed.
|
|
- When an object is deleted, corresponding entry in cache if any is deleted as well.
|
|
- Cache continues to work for read-only operations such as GET, HEAD when backend is offline.
|
|
- Cache disallows write operations when backend is offline.
|
|
|
|
> NOTE: Expiration happens automatically based on the configured interval as explained above, frequently accessed objects stay alive in cache for a significantly longer time.
|
|
|
|
## Limits
|
|
- Bucket policies are not cached, so anonymous operations are not supported when backend is offline.
|
|
- Objects are distributed using deterministic hashing among the list of configured cache drives. If one or more drives go offline, or cache drive configuration is altered in any way, performance may degrade to a linear lookup time depending on the number of disks in cache.
|
|
|