Testing the Fastly CDN
Mar. 7th, 2012 03:19 pm![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png)
Hi all,
This has now been rolled back. It's not working for some subset of users and that is problematic. We are back to how we were earlier!
I've now rolled out a small change that sends a lot of static traffic through Fastly, an interesting CDN service founded by a guy who I used to work with on LiveJournal. It's a neat service that should give us some really good performance gains -- particularly for users who aren't near our main servers in Dallas.
Edit: If you are using something like NoScript or a similar service that whitelists URLs, you will need to add the following domain:
s.dreamwidth.org.a.prod.fastly.net
Many of you noticed that there was about 15 minutes of broken JavaScript on the site. This showed up as cut tags not expanding, the login form not working, and some other weird behaviors. It's fixed now and was caused by me making a typo in the configuration. Sorry about that.
Please let me know if anything else is broken or not working. Also, if the site seems faster, I'd love to know that too. I'm sure
crucially would be interested to hear our opinions of it. :)
This has now been rolled back. It's not working for some subset of users and that is problematic. We are back to how we were earlier!
I've now rolled out a small change that sends a lot of static traffic through Fastly, an interesting CDN service founded by a guy who I used to work with on LiveJournal. It's a neat service that should give us some really good performance gains -- particularly for users who aren't near our main servers in Dallas.
Edit: If you are using something like NoScript or a similar service that whitelists URLs, you will need to add the following domain:
s.dreamwidth.org.a.prod.fastly.net
Many of you noticed that there was about 15 minutes of broken JavaScript on the site. This showed up as cut tags not expanding, the login form not working, and some other weird behaviors. It's fixed now and was caused by me making a typo in the configuration. Sorry about that.
Please let me know if anything else is broken or not working. Also, if the site seems faster, I'd love to know that too. I'm sure