3 ms·
Unless you can move to a host quickly where you'll know exactly how your app can scale, I recommend you cache the hell out of everything possible. What does the
by thomasmallen 18y ago
Unless you can move to a host quickly where you'll know exactly how your app can scale, I recommend you cache the hell out of everything possible. What does the site run on, by the way? Maybe we can offer more specific advice.
- dangrover 18y agoIt's running on PHP 5 in a shared hosting env (Dreamhost). The framework is homegrown, but pretty small. PDO is used as an abstraction later talking to MySQL. It uses Smarty for templating.
- inerte 18y agoCache and/or static pages. DH should be able to handle static pages fine, they're not that bad :p Anyway, ab (apache benchmark) is your friend. Hammer way. It might be that you don't even need any optimization at all.
- danielrhodes 18y agoSmarty has caching in it that is easy to set up. Just use that, and it should be good enough. PHP5 won't be your problem, the database will. If it's your Wordpress site that you are worried about, Wordpress has a caching plugin that is supposed to work if you can get it installed properly. Both of those are file-based caches. If you want to get super ghetto, save a copy of the loaded page that is going to be hit the most and rewrite the URL to that saved static page. Since we're talking about a podcast here, the traffic is most likely going to be distributed over time, so you really shouldn't have to worry that much.
- thomasmallen 18y agoI'm pretty sure he isn't using WordPress.
- thomasmallen 18y agoWhat do you use to cache right now (besides the built-in Smarty caching)?