SleekXMPP/sleekxmpp/xmlstream/matcher
Vijay Pandurangan 6f3cc77bb5 This change stops sleekxmpp from spending huge amounts of time unnecessarily computing logging data that may never be used. This is a HUGE performance improvement; in some of my test runs, unnecessary string creation was accounting for > 60% of all CPU time.
Note that using % in a string will _always_ perform the sting substitutions, because the strings are constructed before the function is called. So log.debug('%s' % expensiveoperation()) will take about the same CPU time whether or not the logging level is DEBUG or INFO. if you use , no substitutions are performed unless the string is actually logged
2011-11-19 11:30:44 -08:00
..
__init__.py More PEP8 compliance cleanups. 2010-10-06 15:12:39 -04:00
base.py Updated all of the matcher classes in sleekxmpp.xmlstream.matcher. 2010-09-01 14:28:43 -04:00
id.py Updated all of the matcher classes in sleekxmpp.xmlstream.matcher. 2010-09-01 14:28:43 -04:00
many.py Updated all of the matcher classes in sleekxmpp.xmlstream.matcher. 2010-09-01 14:28:43 -04:00
stanzapath.py Updated all of the matcher classes in sleekxmpp.xmlstream.matcher. 2010-09-01 14:28:43 -04:00
xmlmask.py This change stops sleekxmpp from spending huge amounts of time unnecessarily computing logging data that may never be used. This is a HUGE performance improvement; in some of my test runs, unnecessary string creation was accounting for > 60% of all CPU time. 2011-11-19 11:30:44 -08:00
xpath.py Updated all of the matcher classes in sleekxmpp.xmlstream.matcher. 2010-09-01 14:28:43 -04:00