News for hackers. Stuff that matters.

A comment on The Mozilla Developer Network has a New Face. Parent comment

Re:The Mozilla Developer Network has a New Face by chad_oliver on Monday December 09, 2013 @04:55PM (#6877329)
Since most pages would be read far more often than they are written, you could probably get good results by 'compiling' the page to a static cache after each edit.
[ Parent | on HN ]
Re:The Mozilla Developer Network has a New Face by ubernostrum on Monday December 09, 2013 @06:27PM (#6877840)
I think you underestimate just how fast and furious the edits can fly on MDN.
[ Parent | on HN ]
Re:The Mozilla Developer Network has a New Face by iagooar on Monday December 09, 2013 @05:41PM (#6877604)
I would go that way too. Static content export, put a CDN in front of it, and response times will get < 100ms, even < 80ms.

I have done some experiments with static exports using dynamic frameworks like Rails, and man, it really makes a huge difference. Of course, if your content is mainly static.

[ Parent | on HN ]
Re:The Mozilla Developer Network has a New Face by lmorchard on Tuesday December 10, 2013 @08:50AM (#6880657)
Rendering page content after edits is exactly what we do. Most page views are served up from a pre-built cache, either from a straight caching HTTP proxy or from a single DB column.
[ Parent | on HN ]