From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; Q312461; .NET CLR 1.0.3705) Description of problem: When operating bind9 as a caching name server on a network where there are thousands of concurrent requests, bind9 shipped with RH7.2 gets unresponsive without utilizing all system resources (network, CPU, Memory). I have confirmed this in a lab. Version-Release number of selected component (if applicable): 9.1.3-4 How reproducible: Always Steps to Reproduce: Send a few thousand concurrent requests to bind9. Actual Results: bind responds to very few requests, network and CPU are alsmost completely idle, there is plenty of free RAM, UDP reveice queue fills up completely (65k). Expected Results: Consume all available system resources, then fill the UDP queue and loose requests. Additional info: I have sent this request to bind9 mailing list and received an answer that I should compile bind9 without threads. Read it at: http://marc.theaimsgroup.com/?l=bind9-users&m=101409787119698&w=2 I have confirmed that by re-compiling bind9 without threads the problem does not exist: bind9 consumes all available system resources before filling up the UDP receive queue and loosing requests.
We believe that the new thread libraries might fix this. Could you attempt it using one of the 8.1 betas?