twisted names is too chatty while resolving names
[email protected] Mon, 14 Sep 2009 13:42:16 -0000
| Newsgroups | gmane.comp.python.twisted.bugs |
|---|---|
| Message-ID | <[email protected]> |
New submission from bra <[email protected]>: Even resolving a single name is just a little bit overkill, from the logging point of view (not to speak about the usability of these), but when doing a lot of resolutions, it affects performance and the health of the user, too: {{{ 2009-09-14 15:11:55+0200 [-] Starting protocol <twisted.names.dns.DNSDatagramProtocol object at 0x28e4ce6c> 2009-09-14 15:11:55+0200 [-] (Port 58178 Closed) 2009-09-14 15:11:55+0200 [-] Stopping protocol <twisted.names.dns.DNSDatagramProtocol object at 0x28e4ce6c> 2009-09-14 15:11:55+0200 [-] <class 'twisted.names.dns.DNSDatagramProtocol'> starting on 51219 2009-09-14 15:11:55+0200 [-] Starting protocol <twisted.names.dns.DNSDatagramProtocol object at 0x28e4ce6c> 2009-09-14 15:11:55+0200 [-] (Port 51219 Closed) 2009-09-14 15:11:55+0200 [-] Stopping protocol <twisted.names.dns.DNSDatagramProtocol object at 0x28e4ce6c> 2009-09-14 15:11:55+0200 [-] <class 'twisted.names.dns.DNSDatagramProtocol'> starting on 41031 2009-09-14 15:11:55+0200 [-] Starting protocol <twisted.names.dns.DNSDatagramProtocol object at 0x28e4cc6c> 2009-09-14 15:11:55+0200 [-] (Port 41031 Closed) 2009-09-14 15:11:55+0200 [-] Stopping protocol <twisted.names.dns.DNSDatagramProtocol object at 0x28e4cc6c> 2009-09-14 15:11:55+0200 [-] <class 'twisted.names.dns.DNSDatagramProtocol'> starting on 19802 2009-09-14 15:11:55+0200 [-] Starting protocol <twisted.names.dns.DNSDatagramProtocol object at 0x28e4cc6c> 2009-09-14 15:11:55+0200 [-] (Port 19802 Closed) 2009-09-14 15:11:55+0200 [-] Stopping protocol <twisted.names.dns.DNSDatagramProtocol object at 0x28e4cc6c> 2009-09-14 15:11:55+0200 [-] <class 'twisted.names.dns.DNSDatagramProtocol'> starting on 15653 2009-09-14 15:11:55+0200 [-] Starting protocol <twisted.names.dns.DNSDatagramProtocol object at 0x28e4ce6c> 2009-09-14 15:11:55+0200 [-] (Port 15653 Closed) 2009-09-14 15:11:55+0200 [-] Stopping protocol <twisted.names.dns.DNSDatagramProtocol object at 0x28e4ce6c> }}} Therefore I propose to lower "noisy" levels and check that variable in protocols too. Patch attached. ---------- Type : enhancement Component: core Keywords : noisy Priority : normal Nosy : ---------- http://twistedmatrix.com/trac/ticket/4021