On Dec 4, 2012, at 11:46 PM, Gerriet M. Denkmann wrote:
> When I add 8 or more operations to NSOperationQueue (using
> NSOperationQueueDefaultMaxConcurrentOperationCount concurrent ops) ,
> - then switch to some other app,
> - then try to make my app active again, I get a beach-ball.
> My app
On 4 Dec 2012, at 18:29, Jens Alfke wrote:
> On Dec 4, 2012, at 3:48 AM, Gerriet M. Denkmann wrote:
>
>> My app creates lots of MyOperations (subclass of NSOperation) and puts them
>> into an NSOperationQueue.
>> I would expect that the app thus remains responsive, but sometimes it is not.
>
On 5 Dec 2012, at 15:57, Joar Wingfors wrote:
> What happens if you remove the "isCancelled" checks?
No effect on blocking.
> How do you create your operation queue?
if ( self.operationQueue == nil )
{
self.operationQueue = [ [ NSOperati
What happens if you remove the "isCancelled" checks?
How do you create your operation queue?
What is the max concurrent operation count of the queue? If
NSOperationQueueDefaultMaxConcurrentOperationCount, what happens if you set it
to (processorCount) instead?
When you take a CPU sample of the pr
On 5 Dec 2012, at 01:29, Jens Alfke wrote:
>
> On Dec 4, 2012, at 3:48 AM, Gerriet M. Denkmann wrote:
>
>> My app creates lots of MyOperations (subclass of NSOperation) and puts them
>> into an NSOperationQueue.
>> I would expect that the app thus remains responsive, but sometimes it is not.
On Dec 4, 2012, at 4:29 AM, Gerriet M. Denkmann wrote:
> My app creates lots of MyOperations (subclass of NSOperation) and puts them
> into an NSOperationQueue.
>
> I would expect that the app thus remains responsive, but sometimes it is not.
>
> A sure way to beach-ball my app is: start it wi
On Dec 4, 2012, at 3:48 AM, Gerriet M. Denkmann wrote:
> My app creates lots of MyOperations (subclass of NSOperation) and puts them
> into an NSOperationQueue.
> I would expect that the app thus remains responsive, but sometimes it is not.
Welcome to the joys of multithreaded programming. :-P
On 4 Dec 2012, at 11:48, Gerriet M. Denkmann wrote:
>
> On 4 Dec 2012, at 18:10, Roland King wrote:
>
>> Can you not run Instruments from the 'Profile' button on Xcode? It should
>> start the process and attach to it and go from there.
>
> I got the Leaks Instrument to work this way (no Le
On 4 Dec 2012, at 18:31, "jonat...@mugginsoft.com"
wrote:
>
>
> On 4 Dec 2012, at 10:29, Gerriet M. Denkmann wrote:
>
>> My app creates lots of MyOperations (subclass of NSOperation) and puts them
>> into an NSOperationQueue.
>>
>> I would expect that the app thus remains responsive, but
On 4 Dec 2012, at 18:10, Roland King wrote:
> Can you not run Instruments from the 'Profile' button on Xcode? It should
> start the process and attach to it and go from there.
I got the Leaks Instrument to work this way (no Leaks) But all other
Instruments just prompted repeatedly for an adm
On 4 Dec 2012, at 10:29, Gerriet M. Denkmann wrote:
> My app creates lots of MyOperations (subclass of NSOperation) and puts them
> into an NSOperationQueue.
>
> I would expect that the app thus remains responsive, but sometimes it is not.
>
> A sure way to beach-ball my app is: start it with
Can you not run Instruments from the 'Profile' button on Xcode? It should start
the process and attach to it and go from there.
On 4 Dec, 2012, at 7:02 PM, "Gerriet M. Denkmann" wrote:
>
> On 4 Dec 2012, at 17:49, Mike Abdullah wrote:
>
>> You have a performance problem. Thus you should use
On 4 Dec 2012, at 17:49, Mike Abdullah wrote:
> You have a performance problem. Thus you should use Instruments to see what
> is going on, rather than hope we can tell you from vague snippets of code.
Maybe I should use Instruments, problem is: I cannot.
I start Instruments, select some templ
You have a performance problem. Thus you should use Instruments to see what is
going on, rather than hope we can tell you from vague snippets of code.
On 4 Dec 2012, at 10:29, "Gerriet M. Denkmann" wrote:
> My app creates lots of MyOperations (subclass of NSOperation) and puts them
> into an N
My app creates lots of MyOperations (subclass of NSOperation) and puts them
into an NSOperationQueue.
I would expect that the app thus remains responsive, but sometimes it is not.
A sure way to beach-ball my app is: start it with a few hundred operations
(which will take about 20 seconds to fin
15 matches
Mail list logo
