Hi, when do you start worrying about scaling and caching?

i will be launching my first rails project soon after i complete
testing, and now being the paronoid programmer i am, i started thinking
about the scaling and caching. when should these defense tactics be
implemented? when my site gets 1000 views, 500,000 views, or 1mill + a
day?

thanks.

On 16 Apr 2007, at 14:56, mixplate wrote:

i will be launching my first rails project soon after i complete
testing, and now being the paronoid programmer i am, i started
thinking
about the scaling and caching. when should these defense tactics be
implemented? when my site gets 1000 views, 500,000 views, or 1mill + a
day?

It all depends on your server: are you using a VPS, dedicated server,
what are the server specs, how complex your application is Â… There
simply is no magic number.

Monitoring your server load should give you an indication on when to
start caching/scaling.

Caching is the first thing you should consider and Rails makes it
very easy to implement and it can be done at any time. There is no
real cost involved (except for your time of course). If I were you, I
would consider it as soon as possible, especially if you’re on a
shared host or VPS. It will make your application more performant,
even when there’s no server load at all.

Best regards

Peter De Berdt

On Apr 16, 5:56 am, mixplate [email protected] wrote:

i will be launching my first rails project soon after i complete
testing, and now being the paronoid programmer i am, i started thinking
about the scaling and caching. when should these defense tactics be
implemented? when my site gets 1000 views, 500,000 views, or 1mill + a
day?

Monitoring is the first step. I use the Robot Co-Op’s libraries for
analyzing Rails log files when written in a special format:

http://nubyonrails.com/articles/2007/01/03/a-hodel-3000-compliant-logger-for-the-rest-of-us