On Mon, Nov 1, 2010 at 5:55 AM, Cal Leeming [Simplicity Media Ltd] <cal.leem...@simplicitymedialtd.co.uk> wrote: > 9 out of 10 times, the bottleneck is usually the database
true, but 8.7 of those 9 are about how the database is used, and not about the engine choice. simply changing SQLite won't improve significantly the one-user case. the trick is: 1) get as few db queries as possible for each page. 2) use appropriate indices for those queries but first of all, you have to identify if it is really the DB where you're spending time. the easiest way to be sure is to install django_debug_toolbar app, it's great to tell you exactly what's going on with the time and the DB accesses. -- 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-us...@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.
