Thank you both. I have finally understood what's going on :).
On Nov 15, 2009, at 7:19 AM, Joar Wingfors wrote:
On 14 nov 2009, at 03.20, Michael Ash wrote:
On Fri, Nov 13, 2009 at 1:28 PM, Paulo Andrade p...@mega.ist.utl.pt wrote:
Hello,
I'm using the CPU sampler template.
Here
On Fri, Nov 13, 2009 at 1:28 PM, Paulo Andrade p...@mega.ist.utl.pt wrote:
Hello,
I'm using the CPU sampler template.
Here (http://1wzi.sl.pt) is a sample of a very simple run to prove my point.
Here's how I collected it:
- Start the app and let it fully launch (it does a few request at
On 14 nov 2009, at 03.20, Michael Ash wrote:
On Fri, Nov 13, 2009 at 1:28 PM, Paulo Andrade p...@mega.ist.utl.pt wrote:
Hello,
I'm using the CPU sampler template.
Here (http://1wzi.sl.pt) is a sample of a very simple run to prove my point.
Here's how I collected it:
- Start the app
Hello,
I'm sampling an iPhone app to detect any bottlenecks in performance.
Interesting thing is that, from the first use of an NSURLConnection the
following method will appear on Instruments:
+[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:]
And it's constantly running,
On 13 nov 2009, at 04.36, Paulo Andrade wrote:
I'm guessing that when using a NSURLConnection the framework spawns a new
thread and creates a runloop for it,
That sounds about right. I could also see that the framework might choose to
keep this thread around after you've finished using it
Hello,
I'm using the CPU sampler template.
Here (http://1wzi.sl.pt) is a sample of a very simple run to prove my point.
Here's how I collected it:
- Start the app and let it fully launch (it does a few request at boot)
- Attach instruments with the CPU Sampler template
- Let it run for 30
