# Configuring a CDN - massive rebake coming up?
**URL:** https://meta.discourse.org/t/configuring-a-cdn-massive-rebake-coming-up/82754
**Category:** Support
**Created:** [3월 11, 2018, 8:51오후 UTC](https://meta.discourse.org/t/configuring-a-cdn-massive-rebake-coming-up/82754 "2018-03-11T20:51:28Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@ljpp](https://meta.discourse.org/u/ljpp)
#### Post date: [3월 11, 2018, 8:51오후 UTC](https://meta.discourse.org/t/configuring-a-cdn-massive-rebake-coming-up/82754/1 "2018-03-11T20:51:28Z")
Continuing the discussion from [Disable CDN causes old images with CDN URL can not be shown](https://meta.discourse.org/t/disable-cdn-causes-old-images-with-cdn-url-can-not-be-shown/29657/2):
> [@Disable CDN causes old images with CDN URL can not be shown](https://meta.discourse.org/t/disable-cdn-causes-old-images-with-cdn-url-can-not-be-shown/29657/2):
>
> The low-CPU usage but slow way
@zogstrip I may looking at a global rebake in the near future, and I have hundreds of thousands of posts. Unless CloudFlare fixes their stuff, I may be switching to KeyCDN or similar.
What does this _low cpu_ method do, and how slow it actually is?
---
### Author:  [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [3월 11, 2018, 9:28오후 UTC](https://meta.discourse.org/t/configuring-a-cdn-massive-rebake-coming-up/82754/2 "2018-03-11T21:28:10Z")
They’ll be rebaked in batches of 500 posts every hour or so instead of rebaking them all as fast as possible 😉
---
### Author:  [@ljpp](https://meta.discourse.org/u/ljpp)
#### Post date: [3월 12, 2018, 6:17오전 UTC](https://meta.discourse.org/t/configuring-a-cdn-massive-rebake-coming-up/82754/3 "2018-03-12T06:17:07Z")
Okay, so we are looking at a month of throttled rebaking 😃
Then again, that is not so critical for Amazon S3 URLs, since the bucket URL will resolve ok, and rebaking would quietly replace the URLs to CDN version over time.
- Can one run this process in the background, start it and forget it?
- Most likely it is interrupted by a Discourse update and/or reboot?
Maybe its better just to rebake the posts that match Amazon S3 URL…
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [3월 12, 2018, 6:35오전 UTC](https://meta.discourse.org/t/configuring-a-cdn-massive-rebake-coming-up/82754/4 "2018-03-12T06:35:21Z")
You can just run a rebake in the console, in fact, if you are making such a drastic move I would strongly recommend you do that.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [3월 12, 2018, 6:36오전 UTC](https://meta.discourse.org/t/configuring-a-cdn-massive-rebake-coming-up/82754/5 "2018-03-12T06:36:54Z")
> [@ljpp](#):
>
> that match Amazon S3 URL…
One moment here… your uploads are on S3? If so then your CDN is going to do nothing to help images unless you define an S3 CDN.
---
### Author:  [@ljpp](https://meta.discourse.org/u/ljpp)
#### Post date: [3월 12, 2018, 6:40오전 UTC](https://meta.discourse.org/t/configuring-a-cdn-massive-rebake-coming-up/82754/6 "2018-03-12T06:40:44Z")
Yes, if I am forced to go the CDN way, I will absolutely do that. Already tried this on a smaller community.
---
### Author:  [@ljpp](https://meta.discourse.org/u/ljpp)
#### Post date: [3월 12, 2018, 7:37오후 UTC](https://meta.discourse.org/t/configuring-a-cdn-massive-rebake-coming-up/82754/7 "2018-03-12T19:37:50Z")
Now rebaking at the rate of 200+ thousand messages per hour. Site is perfectly usable while churning, so not so bad after all.
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [7월 8, 2020, 8:49오전 UTC](https://meta.discourse.org/t/configuring-a-cdn-massive-rebake-coming-up/82754/8 "2020-07-08T08:49:19Z")
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [7월 9, 2020, 6:42오전 UTC](https://meta.discourse.org/t/configuring-a-cdn-massive-rebake-coming-up/82754/9 "2020-07-09T06:42:11Z")