Dear CreativeMornings Community
The following is a list of changes we've made to the site to make to improve performance.
- The entire site is now cached and served from all of Amazon’s 53 edge locations which span US, Europe, Asia, Australia, and South America (all logged out pages, in each language).
- We increased our “worst-case” traffic spike from handling 780 tickets before crashing to 15,197 (almost 20x!)
- Reduced typical page response time from 182 to 65 milliseconds (less than half!)
- Reduced typical CPU usage from 15-40% to 2-5%.
- The site nows uses SSL for greater security (look at that gorgeous green lock icon!), something international users have been asking for.
- We improved autoscaling and increased server capacity to sustain more intense traffic over longer periods of time. In addition, we’ll continue to proactively scale up from 2 to 6 servers Monday mornings (we’re erring on the side of being over-prepared).
- We did several rounds of bug testing. But due to the significant amount of changes (in a short amount of time), it is possible there may be a bug or two yet to discover. Feel free to poke around the site this weekend and let us know if you experience any issues. We’ll be standing by all weekend!
- Cached pages expire from CloudFront after 5 minutes. When admins and organizers make changes, it will be immediately visible to logged in users, but may take up to 5 minutes to reach all logged out users. This is a small tradeoff for a huge performance win.
- Pages can now also cache in the browser. If you return to a page and see stale content, hitting the browser’s refresh button should fix it.
- We had to cut the “Sort by Distance” option on the Cities page, since the page is now cached. However the “Find closest” menu in the header will continue to work.
- To further improve caching, we may want to break languages into subdomains similar to Wikipedia (e.g. en.creativemornings.com,fr.creativemornings.com, etc). This could also allow organizers to more clearly link to content in their preferred language. Known issue until then: if you change your language and return to a previous page, it may appear in the previous language until your refresh your browser.
We’ll continue to monitor performance, but we’re feeling pretty good over here!