I don’t think that was implemented, but Alan would know.
Now, doing something like this gets complicated (or maybe even really, really
difficult), because ATS wants to allocate the cache entry *before* going to the
origin server. Which means, you can’t know the size of the object until you go
Sharding based on domain won't work for us. We use OVH Swift as
backend and there is no option to redistribute based on size or domain
name.
I googled around before writing my first letter and was happy to find
this
I don’t think you can have such control, at least not now. I think the best you
could do is to shard your content (small vs large) into two (or more) domains,
and then you can assign volumes based on those names.
— Leif
From hosting.config:
# Primary destination specifiers are
#
Hi
We are currently using Nginx in front of ATS to store hot content on
NVMe-s, but would like to drop it and only use ATS. ATS is using full
SATA HDD-s to store its content (about 150TB per node) and ATS RAM
cache is disabled entirely.
>From reading ATS documentation, I only found how to enable
