Since the machine isn't even opening up a socket, it makes me think you are hitting either a connection limit or related file limit. Have you set things such as fs.file-max, tcp keepalive, and file limits (check ulimit) per the docs? -----Original Message----- From: 389-users-bounces@xxxxxxxxxxxxxxxxxxxxxxx [mailto:389-users-bounces@xxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of David Boreham Sent: Thursday, February 03, 2011 11:42 AM To: 389-users@xxxxxxxxxxxxxxxxxxxxxxx Subject: Re: [389-users] Performance tuning - where to begin? On 2/3/2011 9:29 AM, Daniel Fenert wrote: > There are plenty of configuration options, where should I look first? > My first guess would be that you've saturated one core. The server probably still processes new connections in a single thread (it did on Unix platforms last time I looked at the code at any rate). So although the CPU load overall is not 100%, once you max out one core, it won't be able to process new connections any faster. That said, the rate you are achieving seems quite low for a modern machine. It would be worthwhile looking to see if it is doing a reverse DNS lookup on the client IP address. After that, try using pstack to see what the accept thread is spending its time on. -- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp -- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users
