Path: utzoo!attcan!uunet!visix!news From: amanda@visix.com (Amanda Walker) Newsgroups: comp.sys.next Subject: Re: DSP compression (was Re: Extended OS Part II) Message-ID: <1990Oct3.182137.24329@visix.com> Date: 3 Oct 90 18:21:37 GMT References: <5122@quiche.cs.mcgill.ca> <1990Oct3.061950.29203@nntp-server.caltech.edu> <1990Oct3.084923.22547@visix.com> <1990Oct3.163742.13055@nntp-server.caltech.edu> Sender: news@visix.com Reply-To: amanda@visix.com (Amanda Walker) Organization: Visix Software Inc., Reston, Virginia Lines: 21 In article <1990Oct3.163742.13055@nntp-server.caltech.edu>, madler@piglet.caltech.edu (Mark Adler) writes: > Monitor shows the CPU at 100% utilization > during a compress or decompress. Am I misreading Monitor? I'm not too familiar with Monitor, but try compiling compres with profiling and looking at where inside the program it's spending its time--on most machines, most of the real time will be spent reading and writing. The CPU certainly has some stuff to do, and it's slightly busier during a compress, but the inner loop of the program is really pretty small once everything has been set up. -- Amanda Walker amanda@visix.com Visix Software Inc. ...!uunet!visix!amanda -- "In this age, the mere example of nonconformity, the mere refusal to bend the knee to custom, is itself a service." --John Stuart Mill, "On Liberty" (1859)