Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In February 2022, we have used 5.2 TB of data for https://mui.com/. Netlify doesn't provide much analytics, so we can only guess why. Now, I did notice behavior that looks completely wrong. The Next's Link component prefetches all the pages for the page that are in the viewport https://nextjs.org/docs/api-reference/next/link. So this means, loading many pages (100?) when only consuming on. This only happens in production:
Mar-06-2022.18-38-28.mp4
https://mui.com/components/alert/
I would expect (hope) this fix to reduce the bandwidth usage by a good 3 TB, saving $600/month. https://deploy-preview-31341--material-ui.netlify.app/components/alert/
Why did I work on this? Because Netlify started to bill $1,000/month for the bandwidth of Material UI last month. We have discovered this a few days ago. Why did it change? It's not clear to me. @mbrookes Do you remember what was the bandwidth guaranteed by Netlify when we moved from Cloudfront in 2018? I thought it was a couple of TB, not 400 GB.
As side historical data, we were using 357 GB of data 3 years ago. I have sent the support of Netlify a new email.