Early Tiger Benchmarks Show Slight Speed-Ups
GatorMarc writes "Geek Patrol has published early speed benchmark tests on Tiger. Despite the fact that Tiger is still in development, the results are promising. Could we see a similar performance improvement as we did upgrading from Jaguar to Panther?"
Was it built with debugging symbols on?
This release was obviously pulled together for the conference -- a Herculean effort by the engineers at Apple to show what will be available in a year for now. A wonderful release for us third-party developers!
No one in their right mind is going to think that this release is fit for benchmarking. There may be some gains that are side effects of internal changes (new versions of gcc, etc.), but anyone with a clue will realize that minimal optimization has been done.
When they say DEVELOPER PREVIEW they mean it...
-ch
Don't most of the speed increases come closer towards the end of the development cycle? I know that is usually the case for games.
Yeah. And Tiger is to be released in the first half of 2005. Which gives them between 5-11 months to make these changes.
I think it's just too early to tell how fast the final release is going to be, since there's probably 3/4 of a year more development to be done.
WARNING: If accidentally read, induce vomiting.
-Sean
Quite. Some even consider premature/early optimization to be a bit of a curse, or at least not a very good idea. In software development in general, definately not just limited to games.
Working toward a usable PDA environment in the spirit of Newton OS: Dynapad
Keep in mind these tests were done on the G5's. Tiger is the only version of Mac OS X to have 64bit support. One has to wonder if it is really faster on non-64 bit operating systems.
Although you do make good points about debug symbols mostly taking a space instead of slowing things down, one can't forget the compiler optimizations that are often enabled in release builds but not enabled in debug builds. Without those optimizations (particularly for C++ apps, as many commercial software products are still C++), some operations may be orders of magnitude slower.
Hence, not suprising that debug builds are often perceived as slower.