On Tue, 2009-03-31 at 06:29 -0700, Ceph wrote: > Under settings.DEBUG=True, django.db.connection.queries is an array of > all queries executed.
For a single request. > Obviously storing every query in text is a > memory hog. Not obvious at all. Storing a few strings doesn't use a lot of memory. > Would it still thrash as much if I wrote my own wrapper > around a DB connection class via settings.DATABASE_ENGINE that > implemented its own DebugCursorWrapper that timed and counted queries, > but did not store the query text? Would the perf hit be as bad? Are you actually seeing a measurable performance hit for storing the queries at the moment? Unless you're running thousands of queries per page (in which case, the logging overhead isn't your problem), this should be barely noticeable. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
