3 ms·
So we just finished a new round of optimizations as part of our ongoing quest to prove that with sufficient caching you can serve arbitrarily large numbers of r
by tlrobinson 18y ago
So we just finished a new round of optimizations as part of our ongoing quest to prove that with sufficient caching you can serve arbitrarily large numbers of requests with arbitrarily slow languages.
http://ycombinator.com/newsnews.html#15jan09 http://ycombinator.com/newsnews.html#15jan09
Is that quest over, or is upgrading the server fair game? :)
- pg 18y agoNo, I'm sure I can squeeze out a lot more performance. But I have a lot of other stuff going on at the moment (Demo Day is this week, among other things) so it is nice to be able to buy my way out of trouble for a change.
- patio11 18y agowith sufficient caching you can serve arbitrarily large numbers of requests Note the collorary: with a sufficient business model you can earn arbitrarily large amounts of money relative to hardware costs. Which always makes me wonder why the clooooooooooooud gets so much press for cost reduction. If your application doesn't value data by weight (or worse, values data at 0), your hosting costs are going to be rounding error. Reducing the rounding error to half-sized doesn't strike me as the number one best use of time for the majority of businesses.
- tlrobinson 18y agoTrue, though reduced hardware cost is only part of the promise of cloud computing. Elastic scalability is a major advantages in some cases, allowing you to rapidly scale up (and back down) while minimizing waste. "The cloud" absorbs the fluctuations. Easy deployment and thus reduced administrative costs might be another. With EC2, etc that's might not be the case, since you still have to set up the OS images and other infrastructure yourself, but things like Heroku might help.