Miscellaneous > The Lounge

CPU wars

<< < (3/8) > >>

mobrien_12:
To be blunt, I do not trust your benchmark results.   You get athlon results two to four times faster than the equivalent Intel chips.  You then say "This shows one thing: Athlon CPUs pwn and Intel CPUs are pieces of shit, My 2.2GHz athlon did almost 6x the work of a 3.2GHz intel ffs!"

If you get discrepancies this wide, you really should be looking at your test.  Nobody survives in the semiconductor world by selling products that are two to four times slower than the competition  at the same prices.   Yet you claim they do, despite the fact that no benchmarking professionals have backed this up.  Is anyone supposed to take this seriously?

How am I supposed to take this seriously when I can get 13,553,853 fps with this  test  out of my 460 MHz Celeron with a wussy 128 kb cache With KDE and Mozilla running, XMMS loaded, and a bunch of other dinky stuff running in the background, and you  get only 15,108,371 with a modern 2.4 GHZ Intel Celeron?  Are you seriously going to tell me that my 460 MHz is almost as fast as that 2.4 GHZ box?  



You also publish NO details about the benchmarks.  What optimization levels did you use?  What compiler?   If you used GCC, did you optimize for cpu architecture with the -march= switch?  Did you run it on systems that had kernels optimized for their chips?  Did you take the SAME binary and run it across platforms?   If not, did you use the same compiler and the same version and the same libraries?  And don't forget about cache!  For heavy FP calculations, a large cache is very important, but you left all that information out.  

Finally, Linux is not UNIX.  UNIX is a family of operating systems which conform to strict written specs created by the Open Group and then are submitted to the Open Group for a rigourous and expensive testing and certification.  Neither Linux nor FreeBSD do that.  They are "unix-like systems" or "*nix" systems, but NOT UNIX.  Those scumbags at SCO are continually trying to convince everyone that Linux is an illegal UNIX. Don't help them out.

solemnwarning:
I also ran the benchmark with xchat, konqueror and xmms running, its compiled with gcc and no optimization flags, my kernel is compiled for K7, but everything else on my machine is for i386

Refalm:

--- Quote from: solemnwarning ---Can admin enable .c, .h, .cpp and .hpp file extentions for upload?
--- End quote ---

Done. The MIME types are set too.

mobrien_12:
If you want to do a "benchmark," give the computer a real-world floating point problem, with real code.  Then see how long it takes to solve it.  For example, invert a 2500x2500 floating point matrix filled with random numbers.  Do a numerical solution of a differential equation.  Do a Fourier transform of an enormously long float array (just make sure that your array dimensions are powers of two, if you want to use the traditional Fast Fourier Algorithm, in case you didn't know that).  

Don't have the skill or time to code that?  Just install or compile GNU Octave.  Optimize it for your architecture if you want, just make sure you optimize it for all of the test archtectures then.  

Here's a one line octave command that will invert a 2500x2500 random matrix using code that's fairly serious and built by pros.  

 
--- Code: ---
octave:1> x=rand(2500);st=cputime();inv(x);et=cputime();et-st
ans = 167.15

--- End code ---


On my old celeron 460 with 128 kb of Cache, running Fedora Core 4, stock kernel, stock FC4  RPM of Octave, it took 167 CPU seconds to run.

A big benchmark script for Octave can be found at http://article.gmane.org/gmane.comp.gnu.octave.sources/56
which lets you see what architecture works best for what kind of calculation.

Demonstrate that an architecture can solve a real world problem significantly faster and then you actually have something to talk about.

toadlife:
Athlon 64 X2 4400+


--- Quote --- %./a.out
In 10 seconds this system has done 48620731 floating-point calculations
%./a.out
In 10 seconds this system has done 50146885 floating-point calculations
%./a.out
In 10 seconds this system has done 77663578 floating-point calculations
%./a.out
In 10 seconds this system has done 56487406 floating-point calculations
%./a.out
In 10 seconds this system has done 75651591 floating-point calculations
%                    

--- End quote ---

This was while compiling in the background. WTF is up with the hugely varied results?

I finished up my compiling and ran it again, and got the exact same scores! I also noticed that only one of my cores was bieng used, so I ran it twice at the same time....


--- Quote --- %./a.out & && ./a.out &
[1] 41530
[2] 41531
%In 10 seconds this system has done 78938919 floating-point calculations
In 10 seconds this system has done 74342611 floating-point calculations

[2]    Done                          ./a.out
[1]  + Done                          ./a.out
%./a.out & && ./a.out &
[1] 41532
[2] 41533
%In 10 seconds this system has done 54624201 floating-point calculations
In 10 seconds this system has done 51831769 floating-point calculations

[2]    Done                          ./a.out
[1]  + Done                          ./a.out
%

--- End quote ---

Again, the scored varied wildly, but at least this time I was able to get both cores working. If you add up the scores from the first one I got 153,281,530

Woohoo!

PS: It's a worthless benchmark

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version