Re: Very large scale sites in Django

2007-06-04 Thread Daniel Ellison
On Sunday 03 June 2007 08:22:10 Tim Chase wrote: > Just as a side note, I believe Akami does geographic cache > controlling in addition to simply caching out of a central > location (as do several other big names in the caching business). > This means that users in, say, China, hit the cache cont

Re: Very large scale sites in Django

2007-06-03 Thread Tim Chase
> The client would dearly love to break its dependence on Akami > caching, and it now looks like we may be able to do so. Thanks > everyone for your help in this. Just as a side note, I believe Akami does geographic cache controlling in addition to simply caching out of a central location (as do

Re: Very large scale sites in Django

2007-06-03 Thread Daniel Ellison
On Saturday 02 June 2007 10:02:08 Simon Willison wrote: > Memcached is pretty much the industry standard now for caching on high > traffic sites, at least those that use the LAMP stack. Flickr and > Wikipedia both use it, but the highest traffic install at the moment > is probably Facebook who are

Re: Very large scale sites in Django

2007-06-02 Thread Simon Willison
On May 31, 5:30 pm, Daniel Ellison <[EMAIL PROTECTED]> wrote: > A quick glance at the memcached site says that it's used on LiveJournal, which > gets over 20,000,000 page requests per day. Excellent. Not quite at our > traffic level, but not too shabby. :) Memcached is pretty much the industry st

Re: Very large scale sites in Django

2007-05-31 Thread Daniel Ellison
On Thursday 31 May 2007 11:44:51 Tim Chase wrote: > It would also be helpful to know things about the usage > patterns--particularly the read-to-write ratio and > currency-demands. > > If most of your hits are reads, and stale data is okay (only > updated every N minutes), then you're a top candid

Re: Very large scale sites in Django

2007-05-31 Thread Tim Chase
>> AFAIK, the bottleneck tends to be the database, so a cache >> solution like memcached should make the deal. Think of a >> 256Mb cache for 10 seconds maybe. > > Yes, the database is generally the main bottleneck these days. > memcached is definitely on my radar. It would also be helpful to kno

Re: Very large scale sites in Django

2007-05-31 Thread Nic James Ferrier
Daniel Ellison <[EMAIL PROTECTED]> writes: > On Thursday 31 May 2007 11:26:37 Nic James Ferrier wrote: >> Daniel Ellison <[EMAIL PROTECTED]> writes: >> > Sounds like this might end up being the highest-traffic Django site there >> > is! :) >> >> Errr... I might be in competition with you there. >

Re: Very large scale sites in Django

2007-05-31 Thread Daniel Ellison
On Thursday 31 May 2007 11:26:37 Nic James Ferrier wrote: > Daniel Ellison <[EMAIL PROTECTED]> writes: > > Sounds like this might end up being the highest-traffic Django site there > > is! :) > > Errr... I might be in competition with you there. > > /8-> Fine. Sounds like this might end up being

Re: Very large scale sites in Django

2007-05-31 Thread Nic James Ferrier
Daniel Ellison <[EMAIL PROTECTED]> writes: > Sounds like this might end up being the highest-traffic Django site there > is! :) Errr... I might be in competition with you there. /8-> -- Nic Ferrier http://www.tapsellferrier.co.uk --~--~-~--~~~---~--~~ You

Re: Very large scale sites in Django

2007-05-31 Thread Daniel Ellison
On Thursday 31 May 2007 10:31:24 John M wrote: > I would love to know your site. Well, I'll reveal that when the site launches, but suffice to say it's for a very popular network TV show. We did the current site and are now redesigning and rearchitecting the entire thing for the next season. D

Re: Very large scale sites in Django

2007-05-31 Thread Daniel Ellison
On Thursday 31 May 2007 09:03:32 Christian Markwart Hoeppner wrote: > AFAIK, the bottleneck tends to be the database, so a cache solution like > memcached should make the deal. Think of a 256Mb cache for 10 seconds > maybe. Yes, the database is generally the main bottleneck these days. memcached

Re: Very large scale sites in Django

2007-05-31 Thread John M
I would love to know your site. On May 31, 5:26 am, Daniel Ellison <[EMAIL PROTECTED]> wrote: > Hi all, > > I'm about to start a Django project that will be replacing an existing > high-profile Drupal site. The existing site has extremely high traffic - > approximately 1,440,000 page views per ho

Re: Very large scale sites in Django

2007-05-31 Thread Christian Markwart Hoeppner
Hi there, AFAIK, the bottleneck tends to be the database, so a cache solution like memcached should make the deal. Think of a 256Mb cache for 10 seconds maybe. Of course, the hardware should be able at least to serve that amount of static pages, and maybe you should think about running the datab

Very large scale sites in Django

2007-05-31 Thread Daniel Ellison
Hi all, I'm about to start a Django project that will be replacing an existing high-profile Drupal site. The existing site has extremely high traffic - approximately 1,440,000 page views per hour, or 400 per second. This is only possible with the help of Akami. Without Akami the site would mel