Am Mi,10.09.2008 um 03:48 schrieb Markus Spoettl:
On Sep 9, 2008, at 5:28 PM, Markus Spoettl wrote:
These numbers come from a test case with 140 objects, when I double
the object number, the test never finishes (at least not within 10
minutes).
OK, I did some more testing and timing and
On Sep 9, 2008, at 8:48 PM, Markus Spoettl wrote:
On Sep 9, 2008, at 5:28 PM, Markus Spoettl wrote:
These numbers come from a test case with 140 objects, when I double
the object number, the test never finishes (at least not within 10
minutes).
OK, I did some more testing and timing and t
On Sep 10, 2008, at 1:04 AM, Markus Spoettl wrote:
On Sep 9, 2008, at 9:36 PM, Seth Willits wrote:
Surely adding 330 items to an array shouldn't take a minute on any
machine from this century. I think your code is doing something
you're not realizing. You could:
a) have a method that on each
On Sep 9, 2008, at 9:36 PM, Seth Willits wrote:
Surely adding 330 items to an array shouldn't take a minute on any
machine from this century. I think your code is doing something
you're not realizing. You could:
a) have a method that on each observation explicitly creates a
bajillion objects
On Sep 9, 2008, at 6:48 PM, Markus Spoettl wrote:
What I don't understand is why adding the auto-release pool has such
a dramatic impact on registering observers on the objects. Anyone
know why?
It would simply be that the methods triggered by KVC/KVO (the
observations) are creating a hug
On Sep 9, 2008, at 5:28 PM, Markus Spoettl wrote:
These numbers come from a test case with 140 objects, when I double
the object number, the test never finishes (at least not within 10
minutes).
OK, I did some more testing and timing and there is a solution - which
I don't understand:
T
Hi List,
I'm having a strange problem with key observing performance, namely
registering observers.
I have an array of objects which is bound to a collection view and its
views register themselves as observers of the array objects'
properties (1 object, 1 view). The objects' properties
