Re: precise timing -- mach_wait_until `drifts`
Re: precise timing -- mach_wait_until `drifts`
- Subject: Re: precise timing -- mach_wait_until `drifts`
- From: Ian Kemmish <email@hidden>
- Date: Tue, 09 Dec 2014 07:27:57 +0000
On 8 Dec 2014, at 21:07, "Mazzaroth M." <email@hidden> wrote:
SUrely what you're actually doing is timing how long it takes to execute:
> [self.delegate highResolutionTimerDidFire];
? If you want to measure how long it takes Mach to wake up your thread, you need to put
> uint64_t mat = mach_absolute_time();
immediately after
> mach_wait_until(next_fire_date);
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Ian Kemmish 18 Durham Close, Biggleswade, Beds SG18 8HZ
email@hidden Tel: +44 1767 601361 Mob: +44 7952 854387
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
_______________________________________________
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