i think the real issue is, why doesnt apple have 800MHz RAM installed by default?!?!
Well, maybe the benchmark that JJP9398 posted here (thanks for that btw) is part of the answer...
Could you make sure, JJP9398, that you run the benchmark with :
- no program running or window open (no safari, no Mail, not anything but Finder)
(The best is to reboot and run the benchmark soon after the reboot)
The results you posted look seriously bad compared with mines (new white macbook with original apple 667Mhz ram, but with the harddrive swapped for a 320Gb WD) :
Results 128.68
System Info
Xbench Version 1.3
System Version 10.5.6 (9G2110)
Physical RAM 2048 MB
Model MacBook5,2
Drive Type WDC WD3200BEVT-00ZCT0
CPU Test 129.94
GCD Loop 227.59 12.00 Mops/sec
Floating Point Basic 109.73 2.61 Gflop/sec
vecLib FFT 90.57 2.99 Gflop/sec
Floating Point Library 160.40 27.93 Mops/sec
Thread Test 241.69
Computation 388.07 7.86 Mops/sec, 4 threads
Lock Contention 175.50 7.55 Mlocks/sec, 4 threads
Memory Test 158.37
System 198.10
Allocate 260.02 954.86 Kalloc/sec
Fill 159.38 7749.28 MB/sec
Copy 199.06 4111.49 MB/sec
Stream 131.92
Copy 125.12 2584.39 MB/sec
Scale 125.75 2598.05 MB/sec
Add 140.22 2986.95 MB/sec
Triad 138.01 2952.39 MB/sec
Quartz Graphics Test 155.79
Line 146.05 9.72 Klines/sec [50% alpha]
Rectangle 184.85 55.19 Krects/sec [50% alpha]
Circle 151.79 12.37 Kcircles/sec [50% alpha]
Bezier 150.50 3.80 Kbeziers/sec [50% alpha]
Text 151.40 9.47 Kchars/sec
OpenGL Graphics Test 127.78
Spinning Squares 127.78 162.09 frames/sec
User Interface Test 223.32
Elements 223.32 1.02 Krefresh/sec
Disk Test 57.05
Sequential 72.21
Uncached Write 92.04 56.51 MB/sec [4K blocks]
Uncached Write 94.80 53.64 MB/sec [256K blocks]
Uncached Read 39.93 11.69 MB/sec [4K blocks]
Uncached Read 111.86 56.22 MB/sec [256K blocks]
Random 47.15
Uncached Write 18.54 1.96 MB/sec [4K blocks]
Uncached Write 124.99 40.01 MB/sec [256K blocks]
Uncached Read 70.19 0.50 MB/sec [4K blocks]
Uncached Read 115.57 21.44 MB/sec [256K blocks]
So could you JJP9398 run the benchmark again ? I strongly suspect, and hope, that some intensive cpu task was already running in the background when you ran the benchmark...
phjo