4 ms·
What's the best way to optimize cost here? Complete site cached and served from memory (no disc access -> faster response times -> scales better)?
by pulse7 10y ago
What's the best way to optimize cost here? Complete site cached and served from memory (no disc access -> faster response times -> scales better)?
- jasoncartwright 10y agoQuick win would be to put CloudFlare in front of it
- ryanlol 10y agoDropping Heroku
- jjoe 10y agoThis was my thinking and experience when I set out to build Cachoid[0]. There's so much to gain from caching stuff in RAM it should be ubiquitous. The thing is CDNs don't always have the scale to stick all tenants in RAM. Hence the caching to disk. [0] - https://www.cachoid.com/ https://www.cachoid.com/
- lucb1e 10y agoFrom the page: > Do we really need three expensive dynos, or a $50/mo database plan? Sounds like there's the chance to optimize for what is, as they say, a static website. Why for a database that you're not using? (And what kind of a database plan do you have when it costs $50/month when it's apparently a (nearly?) empty database?!)