Date: Thu, 4 Jan 2001 19:40:39 -0800 (PST) From: dkelly@hiwaay.net To: freebsd-gnats-submit@FreeBSD.org Subject: ports/24081: CPU utilization of mp3blaster from ports Message-ID: <200101050340.f053edm74100@freefall.freebsd.org> Resent-Message-ID: <200101050350.f053o1G74993@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 24081 >Category: ports >Synopsis: CPU utilization of mp3blaster from ports >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports >State: open >Quarter: >Keywords: >Date-Required: >Class: wish >Submitter-Id: current-users >Arrival-Date: Thu Jan 04 19:50:00 PST 2001 >Closed-Date: >Last-Modified: >Originator: David Kelly >Release: 4.2-STABLE >Organization: n/a >Environment: FreeBSD grumpy.dyndns.org 4.2-STABLE FreeBSD 4.2-STABLE #0: Mon Jan 1 00:19:08 CST 2001 root@grumpy.dyndns.org:/usr/src/sys/compile/GRUMPY i386 >Description: /usr/ports/audio/mp3blaster looks to be an interesting lite mp3 player without the bulk of Gnome or KDE. So it is. But then I noticed my brand spanking new Athlon 800 MHz machine was at 100% CPU utilization playing thru mp3blaster. About 72.0% system, 26.0% user, remainer is other. Sound card is a cheap OEM Soundblaster 128 (ES1371). Not believing this was reasonable, installed the mpg123 port. CPU utilization with mpg123 is essentially nil at 0.49% >How-To-Repeat: Install and run the mp3blaster port. Watch the system with "systat -v" and/or "top -I". >Fix: My guess is the application busy loops rather than block on I/O. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200101050340.f053edm74100>