Re: Performance issues with the DNS patch?

2008-07-28 Thread Damien Miller
On Sat, 26 Jul 2008, J Duke wrote: > I realize that the whole fix to this DNS cache poisoning is to have > random ports and random query ids, and that generating good, strong, > random numbers costs cpu cycles and time. Has anyone else noticed the > performance hit? Anything that I can do? Particu

Re: Performance issues with the DNS patch?

2008-07-28 Thread Ted Unangst
On 7/26/08, J Duke <[EMAIL PROTECTED]> wrote: > I wonder is anyone is seeing performance issues with the patched DNS in the > late snapshots? http://marc.info/?l=bind-users&m=121726908015389&w=2

Re: Performance issues with the DNS patch?

2008-07-27 Thread Daniel Melameth
On Sat, Jul 26, 2008 at 4:12 PM, J Duke <[EMAIL PROTECTED]> wrote: > I wonder is anyone is seeing performance issues with the patched DNS in the > late snapshots? > I installed the July 22 snapshot on our DNS servers, which handle a pretty > heavy load of lookups, mostly for anti-spam action. > > I

Re: Performance issues with the DNS patch?

2008-07-27 Thread Stuart Henderson
On 2008-07-26, J Duke <[EMAIL PROTECTED]> wrote: > I moved back to an earlier version of OpenBSD on the DNS server, and > the Ironport traffic went up to normal, and the DNS lookup failures stopped. > Cpu utilization went back down to around 9%. But I'm vulnerable. Sending spam seems a good way to

Re: Performance issues with the DNS patch?

2008-07-26 Thread Florian Fuessl
mailto:[EMAIL PROTECTED] On Behalf > Of J Duke > Sent: Sunday, July 27, 2008 12:13 AM > To: misc@openbsd.org > Subject: Performance issues with the DNS patch? > > I wonder is anyone is seeing performance issues with the patched DNS in > the > late snapshots? > I installe

Performance issues with the DNS patch?

2008-07-26 Thread J Duke
I wonder is anyone is seeing performance issues with the patched DNS in the late snapshots? I installed the July 22 snapshot on our DNS servers, which handle a pretty heavy load of lookups, mostly for anti-spam action. It was running at 45% or higher cpu utilization after the July 22 snapshot was