News for hackers. Stuff that matters.

A comment on Caching the uncacheable: CloudFlare's Railgun. Parent comment

Re:Caching the uncacheable: CloudFlare's Railgun by marcusf on Monday July 02, 2012 @06:57AM (#4188301)
I'm still not sure how this solves the personalization use case. Usually (I think) the main problem is rendering the page, not pushing it down the wire. So if you still need to render for each request for a personalized page to make sure it's not been updated, where's the gain?

I think I might be slow, but I'm not sure where the wins are here and how you overcome the personalized rendering problem? I'd love for you to talk a bit about it.

[ Parent | on HN ]
Re:Caching the uncacheable: CloudFlare's Railgun by StavrosK on Monday July 02, 2012 @07:05AM (#4188321)
It seems that all the gains are at the point between the upstream server and the CDN node. It has to send fewer packets for the entire page. However, I'm not sure this isn't pretty much as efficient as a large TCP window. Of course, I'm not the one whose job it is to worry about these things, so take this with a grain of salt.
[ Parent | on HN ]