How does Tigris caching work with content-range requests
I’m curious how content‑range requests work with Tigris caching in other regions.
Let’s say I upload a file in North America and then request only a fraction of the file in Europe. Will the cache only cache the fraction requested in the EU, or will it proactively cache the entire file? If the latter is true, will my content‑range request be delayed while the entire file is copied to the EU, or will I get a response as soon as the partial response is ready?
Thanks!
Let’s say I upload a file in North America and then request only a fraction of the file in Europe. Will the cache only cache the fraction requested in the EU, or will it proactively cache the entire file? If the latter is true, will my content‑range request be delayed while the entire file is copied to the EU, or will I get a response as soon as the partial response is ready?
Thanks!
Solution
In most instances, we’ve observed that only a subset of byte ranges are never accessed, rather than entire files being read (either in chunks or as a whole). Adapting to this, the current algorithm caches the entire file, anticipating that additional chunks will be requested in the future. This data movement happens in the background to prevent any latency issues in the request path, i.e., the content‑range request will not be delayed while the file is being moved.
