3 ms·
It completely depends on your application/stack. Something with static content and simple dynamic pages could scream at 256MB, or even less. Something with othe
by gojomo 17y ago
It completely depends on your application/stack. Something with static content and simple dynamic pages could scream at 256MB, or even less. Something with other RAM-eating frameworks and code might run best with GB+.
A nice thing with Slicehost is you can start with the smallest, and then if it seems you need more RAM, can restart the same image on a bigger slice.
You will know if you need more RAM by watching your busy server with 'top' over time, and among other things, ensuring that it never begins swapping.
Almost any app can benefit from more RAM, especially if you use various levels of caching effectively (from the automatic linux disk cache through framework-level fragment- or page- caching to HTTP-server/proxy caching).
So when you're sure things work OK, but then want to make them snappy, throwing RAM at the problem (with a little engineering to use it wisely) is usually a good idea.
- zimbabwe 17y agoOkay, thanks! So you have experience with Slicehost? Moving up to larger slices is a painless task?
- radu_floricica 17y agoAbout a half an hour downtime, in my experience. No work needed.
- gojomo 17y agoYes. My one bump up was a tiny, almost vanilla image and took even less time. And, if continuity of service is important, it's possible to launch the larger clone first, then do a near-instantaneous cutover in various ways (esp. if your site can be read-only for a short window, and you can forward hits from the old machine if DNS takes a while to update).
- patio11 17y agoIt was a matter of minutes for me both times I went from a 256 to 512 slice.
- gtani 17y agoSlicehost makes everything as painless as could be asked for. I had a DNS problem on a new slice yesterday, their folks noticed it within 3 minutes. My understanding is that Xen is pretty tricky admin, but you can do your own ubuntu or CentOS VM under vmware ,give it x Meg RAM, throw ab or jmeter or trample at your app, see what happens.