Imagine! If you watch all of Gregg Pollack’s Scaling Rails tutorials on how to performance tune your rails website, one day you could be the proud owner of a website with performance like this:
Pretty impressive, I’m sure you’ll agree.
DISCLAIMER: This is from Australia on an otherwise decently fast 24Mbps connection. A single page load means nothing, and to be fair, it usually averages around 8 seconds. To be even more fair, this blog takes 12 or 13 seconds to load. Please Gregg, tell me how I can scale PHP!
Tags: envy
February 12th, 2009 at 12:02 am
That is actually the well-known scaling strategy where you make users load many static assets so that your dynamic pages generated by Rails are not hit as frequently.
(Tongue in cheek)
February 12th, 2009 at 12:32 am
Lol, indeed. You should patent that.
Weird, though. The main problem is obviously those javascript files, loading one after the other. Pollack addresses that specific issue in the screencast, why not take your own advice?
And what is even more nutty is that there’s almost no JS in use on the front page, and what there is doesn’t seem to rely on Prototype at all. So why is it even there? Because it was included by default? I just don’t understand these guys.
I don’t want to sound like too much of an asshole but my overriding impression from Pollack & co is that they have no real experience and just come up with this stuff based on last minute research like a school project. Frankly, seeing that they have not implemented any of their suggestions for “scaling rails” on their own web site does not disabuse me of this notion.
Oh well, whatever. Better than nothing, and free! Can’t argue with that, really.
March 14th, 2009 at 12:04 am
Write a page that reads all the js files from disk and minifies them. Use that page in one tag and return caching headers. One request and all the js files are shrunken.