malexgreen
Contributor and PB User
Let talk about this: http://www.haxial.com/spls-soapbox/apple-powermac-G5/
When interpreting these FP results, let us keep in mind that most people use Integer (not FP) most of the time. Therefore, integer results (SPECint) are much more important than floating-point results (SPECfp). In other words, most people should ignore floating-point results because they do not use floating-point anyway (or not much).
SPECfp_base2000 is a single-processor test, so in the following results, where the computer has a second processor, it is either disabled or not used.
I'd say that like with most things on the internet, this article holds no water. The machine is not even out yet and someone is saying it has faked results. I am not saying it is wrong, just that you can produce a lot of fancy looking numbers and "prove" anything wrong these days and with a website people will believe everything written.
He picks only the benchmarks that make the G5 look bad, and completely ignores the ones that show it kicking the P4's a$$.
I guess he didn't watch the keynote stream where not only did Photoshop take 2 times longer to do the same tasks as the dual G5, but the G5 blew it away in 4 or 5 other programs as well.
Mathamatica, Lightwave(? can't remember exactly what prog), some PRO music editing softward(G4 had one CPU at 25% usage and P4 Xeon had 100% CPU usage for the same tasks), and a few other programs all blew away the P4/Xeon.
Photoshop launched in less than a second on the G5(amazing). That might have something to do with the Serial ATA, but the G5s would make it faster anyways.
"You fear in others what you despise in yourself."Originally posted by malexgreen
Let talk about this: http://www.haxial.com/spls-soapbox/apple-powermac-G5/
For one thing, benchmarks should always be taken with a grain of salt, particularly those which span platforms such as Apple's G5 vs. Pentium/Xeon comparisons. They often don't reflect real-world performance -- which is why Apple has presented application comparisons for Photoshop, QuarkXPress, Quake 3, Mathematica, and several other popular apps.
The result? The G5 puts the smack down on the competition. Hard.
Regardless of whether the SPEC numbers may have been boosted on the G5 because Apple used an optimized compiler on the PMG5s and didn't do quite as good a job of optimizing on the Windows machines, the huge performance advantage seen in real-world applications makes this all but totally irrelevant. Not to mention -- many well-known developers have pointed out that benchmarks like SPEC are focused heavily in the CPU(s), and don't take into account very important real-world factors like the G5's 800MHz-2x1GHz frontside busses, Serial ATA hard disks, built-in Gigabit Ethernet, HyperTransport interconnects, et cetera.
Originally posted by malexgreen
Let talk about this: http://www.haxial.com/spls-soapbox/apple-powermac-G5/
That is a strong statement are you saying that they lied about the numbers? Also you do know that many of the "facts" reported by haxial are complete bull? They actually ran the most useful test for me since I would be compiling with GCC on wither of these machines.Originally posted by malexgreen
I just read the veritest report and haxial's page. IMHO, Apple royally screwed up the SPEC numbers. Their SPEC numbers are invalid.
That also showed off the massive bandwidth of that 1GHz bus. which is where the real win is. The Intel chips could not get the data fast enough to keep up even when they did have better SPEC scores.
The WWDC Keynote "bakeoff" using several real world apps, however was telling.
There are two problems with what you are suggesting. First, the tests were done with was was the best machine available. Apple did get a 40 day lead that way but who says Dell will have one of those shipping then.
What I'd like to see Apple do is pair the Intel Compiler/with a 3.2GHz/800MHz FSB system, with a IBM Metroworks/G5 dual 2.0GHz system and rerun the SPEC numbers again. At least then the idea that one machine was more optimized than the other would be an invalid point.