Maintainers:Fastly: Difference between revisions

Line 20:

** Better backbone routing: inter-POP network thanks to [https://docs.fastly.com/guides/performance-tuning/shielding shielding].

** Improved support for large NARs, by streaming results directly from S3 rather than "buffering" them in the POP first. This improves TTFB dramatically.

* Aggressive 404 caching, helping reduce the cost of low ~~negative~~ TTLs ~~on S3~~. ('''STATUS:''' '''MOSTLY DONE''')

* Aggressive 404 caching, helping reduce the cost of misses on S3, which will be very common, especially if users have low TTLs or Hydra is lagging. ('''STATUS:''' '''MOSTLY DONE''')

** Mapping 403s to proper 404s and caching them ('''STATUS:''' '''DONE''')

** Cache aggressive: ~1 month. ('''STATUS:''' '''NOT DONE''' -- requires upstream Hydra tooling changes, so cache uploads have their potential 404s purged in a timely manner.)

@@ Line 20: / Line 20: @@
 ** Better backbone routing: inter-POP network thanks to [https://docs.fastly.com/guides/performance-tuning/shielding shielding].
 ** Improved support for large NARs, by streaming results directly from S3 rather than "buffering" them in the POP first. This improves TTFB dramatically.
-* Aggressive 404 caching, helping reduce the cost of low negative TTLs on S3. ('''STATUS:''' <span style="color:#800080">'''MOSTLY DONE'''</span>)
+* Aggressive 404 caching, helping reduce the cost of misses on S3, which will be very common, especially if users have low TTLs or Hydra is lagging. ('''STATUS:''' <span style="color:#800080">'''MOSTLY DONE'''</span>)
 ** Mapping 403s to proper 404s and caching them ('''STATUS:''' <span style="color:#009000">'''DONE'''</span>)
 ** Cache aggressive: ~1 month.  ('''STATUS:''' <span style="color:#ff0000">'''NOT DONE'''</span> -- requires upstream Hydra tooling changes, so cache uploads have their potential 404s purged in a timely manner.)