Bonus Mastodon Documentation
  • Introduction
  • Mental Health
  • Basics
    • Rules and Culture / Terms of Service
    • Cloud Servers (VMs)
    • Cloud Media Storage (S3 Buckets)
      • Media SubDomain
    • Cloud Email (SMTP)
      • ZeptoMail by Zoho
      • AWS SES
    • Static Content CDN
      • Bunny.net CDN (Pull Zone)
    • Backups
    • Monitoring / Alerting
  • Advanced
    • OS Tuning
    • NGINX Tuning (Reverse Proxy)
    • NGINX Trouble Shooting
    • PostgreSQL 14 Tuning
    • Web (Puma) Tuning
    • Sidekiq Tuning
    • ElasticSearch Tuning
    • Redis Tuning
  • Other
    • Reading Material
    • OS Monitoring
Powered by GitBook
On this page
  • Why?
  • Example
  1. Basics

Static Content CDN

PreviousAWS SESNextBunny.net CDN (Pull Zone)

Last updated 2 years ago

This is one of the most recommended steps and should be taken by all admins regardless of size.

Why?

Using a CDN for static files will take pressure off the nginx/puma webserver when serving commonly available files like JS, CSS, SVG etc, and allows your web server to purely focus on the dynamic important stuff.

Example

I'm running bunny.net CDN, and it's caching more than 95% of the static traffic. Which has dropped my CPU usage massively, and improved the `end user` experience for only a few bucks a month.