home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!sgigate!sgi!twilight!zuni!anchor!olson
- From: olson@anchor.esd.sgi.com (Dave Olson)
- Newsgroups: comp.sys.sgi.misc
- Subject: Re: Where does the CPU go, when its not doing nuthin' (gr_osview)
- Message-ID: <to01eas@zuni.esd.sgi.com>
- Date: 18 Dec 92 02:39:22 GMT
- References: <MBR.92Dec17063936@ponape.bellcore.com>
- Sender: news@zuni.esd.sgi.com (Net News)
- Organization: Silicon Graphics, Inc. Mountain View, CA
- Lines: 20
-
- In <MBR.92Dec17063936@ponape.bellcore.com> mbr@bellcore.com (Mark Rosenstein) writes:
-
- | When looking at gr_osview, I have a program that uses about 50% of the
- | cpu (indigo R4000 elan running 4.05F). The CPU wait line in gr_osview
- | is empty, so if the cpu isn't waiting, why doesn't my program get 100%
- | of the CPU?
- |
- | I guess the less naive way of putting this is: What factors aren't captured
- | between the CPU Usage and CPU wait?
- |
- | [The program in question reads in a 16k chunks of stuff off of disk, messes
- | around with them and writes them out. All to local disk.]
-
- It's hard to say just where it is waiting. Running osview may be
- helpful, as would 'timex -s yourprog'. My guess is that it is indeed
- waiting for the disk part of the time.
- --
- Let no one tell me that silence gives consent, | Dave Olson
- because whoever is silent dissents. | Silicon Graphics, Inc.
- Maria Isabel Barreno | olson@sgi.com
-