On 3/18/2010 5:56 PM, Matt Garretson wrote: > On 3/18/2010 5:15 PM, Kris Deugau wrote: >> Here's one pretty much guaranteed to peg a CPU core for ~130 seconds (or >> http://pastebin.com/2ssy2YEk > > Interesting. I see the same thing as you on that message. There's a > two-minute gap between these two debug lines:
Looking in more detail at the debug output, I see this towards the end (after the delay): async: select found 2 responses ready (t.o.=0.0) async: completed in 120.380 s: URI-A, A:ns1.refactoring.lt. dns: providing a callback for id: 39923/147.36.61.92.zen.spamhaus.org/A/IN async: starting: URI-DNSBL, DNSBL:zen.spamhaus.org.:147.36.61.92 (timeout 15.0s, min 3.0s) async: completed in 120.380 s: URI-A, A:ns4.aleja.lt. dns: providing a callback for id: 34683/6.12.79.77.zen.spamhaus.org/A/IN async: starting: URI-DNSBL, DNSBL:zen.spamhaus.org.:6.12.79.77 (timeout 15.0s, min 3.0s) async: queries completed: 2, started: 2 async: queries active: URI-DNSBL=2 at Thu Mar 18 17:22:45 2010 dns: harvested completed queries It looks like a dns call (or two?) for URI-A took 120 seconds to return. Is that a mere coincdence, or could that be causing a spin of some sort? I can understand a delay caused by slow DNS, but consuming a core seems strange. -Matt
