Caching the uncacheable: CloudFlare's Railgun
blog.cloudflare.com
Caching the uncacheable: CloudFlare's Railgun
1–10 of 71 posts
Re: Caching the uncacheable: CloudFlare's Railgun
#2Pretty cool tech. I guess this can work in parallel with SPDY too. The Internet is evolving a lot lately.
Re: Caching the uncacheable: CloudFlare's Railgun
#3hope they make it available for CloudFlare Pro accounts too.. wait to go cloudflare ..
Re: Caching the uncacheable: CloudFlare's Railgun
#4Would love to see some real world figures on the difference in page loads. Intuitively it feels like a lot of overhead outside of the packets being saved between the host server and cloud flare.
Re: Caching the uncacheable: CloudFlare's Railgun
#5If understand this correctly:
1. You install "Railgun" on your publishing web server
2. It pushes deltas of your webpage to CloudFlare
3. Who then update their cache of your webpage across their CDN.
It seems as though folk are starting to see that in most environments caching ought to be driven by POSTs, not GETs + timeouts.
Re: Caching the uncacheable: CloudFlare's Railgun
#6Delta encoding for HTTP has been proposed since 2002[0], but seems to have been lukewarmly received.
A fully server-side solution will probably bypass most problem cases, but might solve some, so I hope CloudFlare looks into contributing to a distributed standard solution.
Re: Caching the uncacheable: CloudFlare's Railgun
#7Would love to see some real world figures on the difference in page loads. Intuitively it feels like a lot of overhead outside of the packets being saved between the host server and cloud flare.
I do have some numbers on load times based on testing we did with a hosting partner where we took a small number of their sites and tested using Railgun. We saw a speedup of between 2.77x and 4.78x on the page download time.
With a different hosting partner (and a different set of sites) we saw a page download time speedup of between 2.94x and 8.12x.
Re: Caching the uncacheable: CloudFlare's Railgun
#8If understand this correctly: 1. You install "Railgun" on your publishing web server 2. It pushes deltas of your webpage to CloudFlare 3. Who then update their cache of your webpage across their CDN. It seems as though folk are starting to see that in most environments caching ought to be driven by POSTs, not GETs + timeouts.
> It seems as though folk are starting to see that in most environments caching ought to be driven by POSTs, not GETs + timeouts.
HTTP supports that too (through ETag and 204 Not Modified).
Re: Caching the uncacheable: CloudFlare's Railgun
#9so railgun is internally sending diffs. I would have thought caching companies were doing that already, but it seems I'm wrong.
That being said, I'd have used another name ;à
Re: Caching the uncacheable: CloudFlare's Railgun
#10This looks rather interesting... Does any fully server-side solution such as varnish have any similar functionality? Seems like a no-brainer.