On Sep 17, 10:25 am, Simon Willison <si...@simonwillison.net> wrote: > That's 0.0006 of a second overhead for a page logging 100 SQL > statements. The performance overhead will go up if you attach a > handler, but that's fine - the whole point of a framework like > 'logging' is that you can log as much as you like but only act on > messages above a certain logging level. I woudln't worry about performance, lately I had a project doing massive logging, which resulted in a performance loss, but replacing my logging functions with simple lambda functions doing nothing (eg replace django.core.log.warn with lambda *args, *kwargs: pass if loglevel is error) gave me quite a performance boost.
Aide from that: +1 on the proposal. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
