From owner-freebsd-current Thu Jan 28 13:30:48 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19901 for freebsd-current-outgoing; Thu, 28 Jan 1999 13:30:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19892 for ; Thu, 28 Jan 1999 13:30:44 -0800 (PST) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id QAA13214; Thu, 28 Jan 1999 16:30:30 -0500 (EST) Date: Thu, 28 Jan 1999 16:30:30 -0500 (EST) Message-Id: <199901282130.QAA13214@highwind.com> From: HighWind Software Information To: current@FreeBSD.ORG Subject: Locked at 100% User CPU Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In libc_r, I don't think the code in uthread_kern.c's _thread_kern_select() scales at all. As the number of network connections (TCP) to my application grows, I believe this routine takes longer and longer and my CPU goes to 100% user space. Something makes me believe that this routine has an n^2 (or worse) problem. Seems to relate to the number of fd's to select() on. At about 300-400, even a P2 400Mhz gets max'd out and gets nothing done. Anybody have a feeling as to what is wrong here? -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message