Re: check memory consumption (kernel address space) and cpu consumption by kext
Re: check memory consumption (kernel address space) and cpu consumption by kext
- Subject: Re: check memory consumption (kernel address space) and cpu consumption by kext
- From: Wade Tregaskis <email@hidden>
- Date: Fri, 19 Jun 2009 13:28:04 -0700
You can use the trace facility (kdebug) to emit trace markers, and then use the trace tool to look for and measure these markers. You may also be able to use Instruments to do more intelligent things with them (I have not played with this aspect of Instruments). You can use trace markers for many things - obviously you can emit them when you begin and end work, and measure the distance between them to determine how long your work took. You can emit them when you allocate and free memory, and count the alloc/free pairs to determine how much memory a given unit of work consumes.
More to the point, do this and then use System Trace in Shark to see it all happening. See the System Tracing chapter of the Shark user guide, including the Sign Posts section on how to generate the aforementioned events.
Wade |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden