argo billed bandwidth different than traffic bandwdith
New to cloudflare. Last 7 days total bandwidth shows 162GB, Argo billing month to date shows 32GB. "How billing works" page broken.
Site is configured DNS only, no proxy.
Also Cache is 0%, is it since Tiered Caching is
off. Seems like a suitable default on?12 Replies
Site is configured DNS only, no proxy.If there's no proxy records at all, then Argo won't help you and you wouldn't see any traffic in CF. Something must be proxied
is it since Tiered Caching is off.Tiered Caching won't help you if you're getting no cache at all. You also won't get cache unproxied. By default only specific resources (css/js/images) are cached, you can use cache rules to cache html as well if not dynamic in your setup https://developers.cloudflare.com/cache/concepts/default-cache-behavior/
Thanks, I'll dig deeper
Things work well now cache rate nearly 90%. All proxy. One thing I’m seeing a concern with is traffic pull from CF.
CF is pulling in 20GB per hour from my origin consistency Vs the earlier CDNs 1GB per hour at peak. Any thoughts?
What do you mean "earlier CDNs"?
The first thing that comes to mind is -- one of CF's big advantages and also shortfalls is that they have so many locations. Some ~350 Colos all with their own cache.
You mentioned Tiered Caching above. Smart Tiered Caching would help with this, as long as none of your origins are anycast/geodns with a ton of ips (otherwise it may get confused and route more sub-optimally)
I'll try Tiered Caching, thanks! This is 1d of origin servers bandwidth to CF. Im not really sure why the spikes in pulling from origin.
One guess would be if you have a ton of frequently requested assets with the same ttl, they'd all expire at the same time
That sounds fair. I'll update Cloudflare to override cache to 2 days since I have query string bursting.
The wording here was a bit confusing, does this mean I would use Standard?
No query string
Ignore query string
Standard
If you want it to be part of the cache key yea
https://developers.cloudflare.com/cache/how-to/set-caching-levels/
Cloudflare Docs
Caching levels · Cloudflare Cache (CDN) docs
Caching levels determine how much of your website’s static content Cloudflare should cache. Cloudflare’s CDN caches static content according to the …
CF still pullling in agresseively from the origin, which has a 2-day TTL and 96% cache HIT rate.
I've also switched off any other CDN directly reaching the server.
Any suggestions on what to look for to optimise?
96% is pretty good, still a bit lower then I would think if they're 2d cached and it's just from the r2 hostname. You don't have Pro right?
Getting Pro is next. I'm trying out a bunch of toys like Images/Stream and Argo to see which product I need to write the check to