-
Notifications
You must be signed in to change notification settings - Fork 49
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
Add support for aged cache directories #131
Comments
I don't think this is configurable on nginx |
+1; this thought has crossed my mind as well.
It's probably just something we would have to "build" (as in, code out, with "domain knowledge"), not something Nginx could automagically "just do" for us with config. |
Yeah if theres interest in this maybe I'll take a crack it over the winter break, I've got a new server on with 8tb of NVMe and another 8tb of HDE I'd like to take advantage of (I know in practice right now the cache depth is likely to all fit inside the first 8tb of NVMe but you know the "future") :) |
@holdenk I suspect The Way To Go on this is probably https://man.archlinux.org/man/lvmcache.7 - WDYT? |
Eg on some servers there is X TB of NVMe and Y TB of SSD and K TB of HDD and it would be nice to have expiration just slowly move data down the stack in terms of speed.
The text was updated successfully, but these errors were encountered: