Yup. the application performance has been kept in mind from the ground work. Zero or one query, with extensive use of cache is what we try to achieve at the app level.
Just to keep the thread a bit more focused on it's purpose, I would like to remind ourselves that, the discussion is on "Scaling django installation" and not "Scaling django application". For e.g. (with random number representations) - Setup 1: Single server setup: x1 Computation Units, x2 GB memory, n Geographical location, Max Serves 2000 requests/sec - Setup 2: 2 servers cluster setup (1 server serving django, other media): y1 Computation Units, y2 GB memory, n Geographical location, Max Serves 3000 requests/sec - Setup 3: 2 servers cluster setup (with a single load balancer): z1 Computation Units, z2 GB memory, n Geographical location, Max Serves 2800 requests/sec Hope, I was able to put things in the right direction. On Fri, Jun 1, 2012 at 7:43 PM, Javier Guerra Giraldez <jav...@guerrag.com>wrote: > On Fri, Jun 1, 2012 at 3:56 AM, Subhranath Chunder <subhran...@gmail.com> > wrote: > > how should we measure response complexity? > > a simple first approximation is the number of DB queries per page. > the debug toolbar nicely gives that figure while developing. > -- > Javier > > -- > 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 > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- Thanks, Subhranath Chunder. www.subhranath.com -- 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 django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
