rah, rah, rah - I'll just pile on with the VPS solutions - but with the obvious addition: TEST IT.
It's pretty straightforward to get the processing time, including the time of the queries, using all the django goodness that's already in place. At 20 page requests a second that aren't static/cached content (Lighttpd, NGInx, etc) - you've got a service time of up to 50 ms, assuming that you're processing these guys linearly - which you likely won't, but lets take that as a starting point. Give yourself 10 clients (prefork mod-python, or child processes in Lighttp/FCGI) and you can let that breathe up to 500ms, which should be more than enough. Loading up the database with fake data and then driving a load test will give you the best numbers, and let you tune/know for sure what's happening. We've had excellent experience with virtual private servers (a small company in Seattle that's hosting our stuff) and responsiveness, plus it's a hell of a lot cheaper than buying, racking, and doing all the hardware bits yourself. -joe On 4/27/07, RajeshD <[EMAIL PROTECTED]> wrote: > > > > > On Apr 27, 8:16 am, "Benjamin Slavin" <[EMAIL PROTECTED]> > wrote: > > On 4/27/07, Nicola Larosa <[EMAIL PROTECTED]> wrote: > > > > > You may consider starting with a virtual server, and then moving to > > > dedicated ones when the traffic warrants it. > > > > I second the recommendation to go with a virtual server as a starting > > point. > > I third this :) > > Have you considered Joyent/Textdrive's Accelerator hosting? It's > designed to address just such issues of scalability. > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
