Re: Cocoa/Objective-C's Relative Performance
Re: Cocoa/Objective-C's Relative Performance
- Subject: Re: Cocoa/Objective-C's Relative Performance
- From: Guy English <email@hidden>
- Date: Wed, 12 Jan 2005 17:06:23 -0500
On Wed, 12 Jan 2005 16:12:33 -0500, Ivan S. Kourtev
<email@hidden> wrote:
> Well, that is sort of what we did and how we found out we need this
> performance information.
I don't know of any benchmarks for the Cocoa collection classes. What
performance problems are you seeing and with which classes? It is
likely possible to write a collection class optimized for your
particular data access pattern and then drop it in where you need it.
If it follows the Cocoa collection methods it should be pretty
painless. You can also poseAs but I'm not sure that's a good idea
against class clusters. In fact I'm pretty sure it's a bad idea. :)
So I guess the answer to your question is another question: What is
Shark telling you?
> Personally, I also prefer to think in advance about the potential
> bottlenecks and performance issues in order to avoid unnecessary
> re-engineering efforts.
That's fair enough but it's not often that optimizing the collection
classes will gain you much. Choosing a different algorithm often works
better.
The idea behind writing first then optimizing hot spots is that you've
shortened your development time enough by using the provided classes
that you've got time to go back and optimize. The theory is a net gain
in terms of implementation time.
Guy
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden