On Fri, Mar 21, 2008 at 12:13 PM, John Stiles <[EMAIL PROTECTED]> wrote: > Michael Ash wrote: > For what it's worth, I wrote a quick test program creating 50,000 > random key/value pairs of NSStrings of around 500 characters each, > then inserted them into an NSDictionary. My quick code compiled with > no optimizations took 200 milliseconds to insert all 50,000 strings > into an NSMutableDictionary. This is admittedly on a much faster > machine (a 2.66GHz Mac Pro) and your objects may have been > substantially more complex to hash or compare, but the above does not > build a convincing case for the STL option in my mind. > You're only comparing apples and oranges if you don't port your test code > to STL and test it yourself. > There's simply no such thing as a fair comparison between a G4 running on > battery power and an Intel Xeon.
I never claimed otherwise. I simply find it odd when people act as though good performance on tens of thousands of records were somehow exceptional or difficult. It was such once upon a time, but with modern CPUs and good data structures easily available in libraries, it really isn't anymore. But just for fun, I implemented a std::map version of my test as well. Both versions take somewhat under 200ms, with the differences between them completely overwhelmed by per-run variances. The lesson here, as usual, is to Optimize Later. Use what produces the best code and what you're most comfortable with. For me that means staying far, far away from the STL. For others it may mean using ObjC++ and the STL over Cocoa collection classes. But choosing one over the other for speed when you don't have working code yet is putting the cart before the horse. Mike _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
