> Maybe your caching strat of you OS isn't best for your use case.
On the other hand the OS does know about memory pressure from IO and from heap memory for the whole system. This crate will only know about cache pressure within a single process.
> Also, you may use a network file system
Which can also be set to do aggressive caching, at the expense of consistency.
> and want your cache warm up to be tuned up and consistent.
the description doesn't say that it's doing cache warmup any more eagerly as regular reads would
The benefit of bringing something in process is as always more control, and usually at the expense of having to make decisions with less data about the rest of the system than an OS level service would have.
Sometimes you need very explicit control over when things are read from cache and when they aren't. This can be hard with network file systems. Especially when you have two different use cases on the same filesystem, which isn't that odd, even within a single application.
On the other hand the OS does know about memory pressure from IO and from heap memory for the whole system. This crate will only know about cache pressure within a single process.
> Also, you may use a network file system
Which can also be set to do aggressive caching, at the expense of consistency.
> and want your cache warm up to be tuned up and consistent.
the description doesn't say that it's doing cache warmup any more eagerly as regular reads would