Yes, you can load balance between slices, AND you can pool your bandwidth between them (new Slicehost feature).
@NoviceSortof: Yes, I am running a Hardy install with 256 MB. My typical 'top' breakdown looks like: - 55% Apache (prefork) - 10% nginx - 5% mysql - 5% postgres - 5% et al. So my allocation is around 80%, but 'free' shows the actual usage (buffers/cache) to hover around 50%. I'm not entirely sure how those two metrics relate. On Oct 8, 7:32 am, Finder <[EMAIL PROTECTED]> wrote: > I'm on slicehost with one 256 slice, and one 512...running Django on > the 256 with lighttpd and my forums, email, etc on the 512 with apache > So far Django has still preformed great and when I ran load tests, > lighttpd with Django handled the load very well. We're up to about > 3,000 hits per day no problem (I know...not many, but still as much as > typical personal sites get). Php-cgi on lighttpd seemed to hit its cap > and started throwing random errors though which is why I moved it off > on apache. > > One nice thing is that if you find yourself needing more, you can load > balance...just get another slice, mirror your django, set up one as > the database server, change lighttpd configuration to point to two > IP's, and you're now load balancing between two django servers with > one lighttpd. (same with apache I believe) > Or increase memory and harddisk quickly if required > > On Oct 6, 1:30 pm, Jeff <[EMAIL PROTECTED]> wrote: > > > I am about to begin a new Django project and I am currently evaluating > > hosting options. I know there has been a number of discussions on this > > topic, and I have read most of them. However, seeing how quickly > > things change in the web development / hosting world, I wanted to get > > some opinions if the following summary still holds true. > > > The most useful information I have found on Django hosting was > > here:http://www.djangoproject.com/weblog/2008/jan/12/mt/ > > > From this, and other sources, I believe the best hosting options to > > be: > > > 1. Web Faction - for those that want to get Django up and running as > > quickly and easily as possible, using their automated setup. > > > OR > > > 2. Slicehost - for those that want COMPLETE control of their hosting > > environment. Only drawback (for some) is that everything needs to be > > installed from scratch. > > > In the case of Slicehost, I am also curious if the 256 slice is > > sufficient for most Django apps. > > > I appreciate any thoughts or comments. > > > Thanks! > > > Jeff --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
