Re: OT: Top with history
Re: OT: Top with history
- Subject: Re: OT: Top with history
- From: Jens Alfke <email@hidden>
- Date: Wed, 5 Oct 2005 23:53:13 -0700
On 5 Oct '05, at 7:29 PM, Marc Van Olmen wrote:
But, on one of our configurations we have drop frames/audio because during a period of a minute there is some heavy cpu usage. This thing happens like once or twice a week.
One suspect might be the weekly disk scan to update the database used by the 'locate' command. This doesn't use a lot of CPU but does hit the disk a lot. According to 'man locate', the weekly script is /usr/libexec/locate.updatedb. I am not sure how to disable this. On my own system I would use Top -u to see which process is taken all that cpu usage. But because this cpu usage peak is randomly I would like to have some kind of application that does something like Top -u and writes it every xx seconds to disk..
Use:
top -l 0 > top.log &
The "-l" flag enables "logging" mode, which just dumps the output to stdout every second. I think there are other options to configure how often it writes and which processes it will show; check the 'man' page for details.
--Jens |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden