From owner-freebsd-hackers Wed Apr 18 12:47:43 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id A1C6037B422 for ; Wed, 18 Apr 2001 12:47:39 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id f3IJlYd82416; Wed, 18 Apr 2001 12:47:34 -0700 (PDT) Date: Wed, 18 Apr 2001 12:47:34 -0700 (PDT) From: Doug White To: Charles Sprickman Cc: Subject: Re: Shoutcast, high cpu, threads In-Reply-To: Message-ID: X-All-Your-Base: are belong to us MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 17 Apr 2001, Charles Sprickman wrote: > Hi, > > I'm running shoutcast on a 4.2R machine, and I'm finding that the > shoutcast server, when idle climbs up to around 90% cpu usage. Included > is a bit of back-and-forth with a shoutcast support person. Does sc_serv use select() in it's main loop? I've seen applications that use a zero timeout for select() and when they're idle the select() loop runs really fast. This certainly sucks for multiuser systems but for dedicated boxes it allows for great response time. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message