> To be fair (because otherwise somebody will claim I'm missing an obvious > point), yes, this could be done via syslog on systems that have it > available. It is still a performance hit (writing to disk isn't free). I > did an experiment early last year to put in calls to the python logging > module throughout various paths in Django. It had a noticeable impact.
As author of the logging package in Python and a (new) Django user, I'm very interested in this. Can you give me a little more information? What sort of impact did it have, quantitatively speaking? Did you use e.g. logger.isEnabledFor() to avoid computing the arguments unnecessarily? I would like to see if it is possible for Django to use Python logging (perhaps only in debug mode), and if there are bottlenecks which preclude this, I would like to see what can be done to improve matters - so I would appreciate your feedback. Thanks, Vinay Sajip --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
