iPhone背景线程与计时器性能

Question

One of our requirment can be implemented either by running a NSTimer every 30 mins or a background thread/job, which polls specific application 'state' every one minute.

But I am wondering how CPU intensive this background job compared to NSTimer, if NOT much of a difference then we will go for background threads/jobs.

Thanks

Answer 1

Threads are very lightweight.

In fact you could very well do the NSTimer polling on main thread and then use GCD to perform the actual work on a private serial queue (on another thread) using an inline block. That way your code remains very readable while you do not sacrifice any performance.

Note that NSTimer does not guarantee exact timing precision, but I assume that is not important.