First run @378x9 DDR2-757 was 3-3-3-10 1:1. The run @ 400x9 DDR2-1200 is 5-5-5-15 2:3 divider.
Printable View
First run @378x9 DDR2-757 was 3-3-3-10 1:1. The run @ 400x9 DDR2-1200 is 5-5-5-15 2:3 divider.
@KTE - cool man, XP 32 or 64?
Sorry, 32-bit for both.
Added above for clarity.
I did the run while Folding two SMP...Quote:
---------- RUN1PASS1.LOG
encoded 1442 frames, 51.74 fps, 3904.94 kb/s
---------- RUN2PASS1.LOG
encoded 1442 frames, 51.29 fps, 3904.94 kb/s
---------- RUN3PASS1.LOG
encoded 1442 frames, 32.94 fps, 3904.94 kb/s
---------- RUN4PASS1.LOG
encoded 1442 frames, 51.03 fps, 3904.94 kb/s
---------- RUN1PASS2.LOG
encoded 1442 frames, 13.12 fps, 3974.08 kb/s
---------- RUN2PASS2.LOG
encoded 1442 frames, 13.07 fps, 3974.08 kb/s
---------- RUN3PASS2.LOG
encoded 1442 frames, 13.14 fps, 3974.08 kb/s
---------- RUN4PASS2.LOG
encoded 1442 frames, 13.07 fps, 3974.08 kb/s
I'll see if it makes any difference with Folding closed.
2 x E5420 stock on D5400XS 8GB FB DIMM DDR2 800 4 Raptor RAID0
Same settings with Folding closed
Quote:
---------- RUN1PASS1.LOG
encoded 1442 frames, 57.91 fps, 3904.94 kb/s
---------- RUN2PASS1.LOG
encoded 1442 frames, 58.18 fps, 3904.94 kb/s
---------- RUN3PASS1.LOG
encoded 1442 frames, 58.17 fps, 3904.94 kb/s
---------- RUN4PASS1.LOG
encoded 1442 frames, 58.11 fps, 3904.94 kb/s
---------- RUN1PASS2.LOG
encoded 1442 frames, 28.09 fps, 3974.08 kb/s
---------- RUN2PASS2.LOG
encoded 1442 frames, 28.13 fps, 3974.08 kb/s
---------- RUN3PASS2.LOG
encoded 1442 frames, 28.22 fps, 3974.08 kb/s
---------- RUN4PASS2.LOG
encoded 1442 frames, 28.15 fps, 3974.08 kb/s
@CyberDruid - nice system dude. FSB = 333 and RAM = 800? So 5:6 divider then? Also, which O/S and 32 or 64 bit?
Sorry forgot to specify. This board is weird the RAM always runs at DDR2 800...no way I can see to OC it...raising the FSB does not seem to change the RAM speed. Not sure how that works to be honest...I've got very limited OC-ability on the Xeons...I can jack them to 7.5 x 389.
They are running at 7.5 x 333 and I am using Vista Ultimate 64 bit.
Quote:
---------- RUN1PASS1.LOG
encoded 1442 frames, 68.82 fps, 3904.94 kb/s
---------- RUN2PASS1.LOG
encoded 1442 frames, 69.70 fps, 3904.94 kb/s
---------- RUN3PASS1.LOG
encoded 1442 frames, 69.49 fps, 3904.94 kb/s
---------- RUN4PASS1.LOG
encoded 1442 frames, 69.18 fps, 3904.94 kb/s
---------- RUN1PASS2.LOG
encoded 1442 frames, 33.26 fps, 3974.08 kb/s
---------- RUN2PASS2.LOG
encoded 1442 frames, 33.30 fps, 3974.08 kb/s
---------- RUN3PASS2.LOG
encoded 1442 frames, 33.34 fps, 3974.08 kb/s
---------- RUN4PASS2.LOG
encoded 1442 frames, 33.38 fps, 3974.08 kb/s
That's with the Xeons clocked to 7.5 x 388 CPU-Z does not read the RAM.
@cyber - is it still 5:6 or since you said it runs @ 800, then 1:1?
Here's one of my rigs.
http://img.photobucket.com/albums/v31/canny/x264_a.jpg
Q6600
Vista x64
x38 chipset
5-5-5-15 SPD
@3.33GHz
Quote:
---------- RUN1PASS1.LOG
encoded 1442 frames, 66.50 fps, 3904.67 kb/s
---------- RUN2PASS1.LOG
encoded 1442 frames, 66.19 fps, 3904.67 kb/s
---------- RUN3PASS1.LOG
encoded 1442 frames, 67.14 fps, 3904.67 kb/s
---------- RUN4PASS1.LOG
encoded 1442 frames, 67.18 fps, 3904.67 kb/s
---------- RUN1PASS2.LOG
encoded 1442 frames, 18.55 fps, 3952.97 kb/s
---------- RUN2PASS2.LOG
encoded 1442 frames, 18.46 fps, 3952.97 kb/s
---------- RUN3PASS2.LOG
encoded 1442 frames, 18.47 fps, 3952.97 kb/s
---------- RUN4PASS2.LOG
encoded 1442 frames, 18.80 fps, 3952.97 kb/s
@3.60GHz
I was loading another program during run4pass1, thats why it dropped to 56 :p:Quote:
---------- RUN1PASS1.LOG
encoded 1442 frames, 71.49 fps, 3905.42 kb/s
---------- RUN2PASS1.LOG
encoded 1442 frames, 72.03 fps, 3905.42 kb/s
---------- RUN3PASS1.LOG
encoded 1442 frames, 71.66 fps, 3905.42 kb/s
---------- RUN4PASS1.LOG
encoded 1442 frames, 56.30 fps, 3905.42 kb/s
---------- RUN1PASS2.LOG
encoded 1442 frames, 20.22 fps, 3952.85 kb/s
---------- RUN2PASS2.LOG
encoded 1442 frames, 20.27 fps, 3952.85 kb/s
---------- RUN3PASS2.LOG
encoded 1442 frames, 20.30 fps, 3952.85 kb/s
---------- RUN4PASS2.LOG
encoded 1442 frames, 20.25 fps, 3952.85 kb/s
It looks like Vista is indeed slower than XP reading these results.
question... how do you aquire a skulltrail mobo.... i'd love to get a hold of one w/ two xeons
---------- RUN1PASS1.LOG
encoded 1442 frames, 73.65 fps, 3905.42 kb/s
---------- RUN2PASS1.LOG
encoded 1442 frames, 74.55 fps, 3905.42 kb/s
---------- RUN3PASS1.LOG
encoded 1442 frames, 74.43 fps, 3905.42 kb/s
---------- RUN4PASS1.LOG
encoded 1442 frames, 74.55 fps, 3905.42 kb/s
---------- RUN1PASS2.LOG
encoded 1442 frames, 20.35 fps, 3952.85 kb/s
---------- RUN2PASS2.LOG
encoded 1442 frames, 20.38 fps, 3952.85 kb/s
---------- RUN3PASS2.LOG
encoded 1442 frames, 20.40 fps, 3952.85 kb/s
---------- RUN4PASS2.LOG
encoded 1442 frames, 20.42 fps, 3952.85 kb/s
@G H Z - thanks for the results... what chipset is your board and what o/s (also 32 or 64 bit)?
@dkx64 - first run is 9x370 and 2nd is 9x400? Also, what is your mem speeds for each run (not timings but speed)?
@toysoldier - got it thanks!
I remember 3.60 was 9x400 @ 1066mhz ram.
I forget what the ram speed was at 3.33, but i've ran it again at 3.42. Use these results instead:
Q6600 @3.42 9x380 - 1013mhz RAM
Quote:
---------- RUN1PASS1.LOG
encoded 1442 frames, 69.82 fps, 3905.42 kb/s
---------- RUN2PASS1.LOG
encoded 1442 frames, 68.52 fps, 3905.42 kb/s
---------- RUN3PASS1.LOG
encoded 1442 frames, 69.19 fps, 3905.42 kb/s
---------- RUN4PASS1.LOG
encoded 1442 frames, 69.29 fps, 3905.42 kb/s
---------- RUN1PASS2.LOG
encoded 1442 frames, 19.30 fps, 3952.85 kb/s
---------- RUN2PASS2.LOG
encoded 1442 frames, 19.33 fps, 3952.85 kb/s
---------- RUN3PASS2.LOG
encoded 1442 frames, 19.33 fps, 3952.85 kb/s
---------- RUN4PASS2.LOG
encoded 1442 frames, 19.32 fps, 3952.85 kb/s
got it man, thanks!
i like this benchmark, really goes to show how little significance ram clocking over 1:1 has.
looking at the Q6600 9x400 results having DDR2-800 44412 ram vs. DDR2-1200 55515 ram only equals 1.x fps increase.
this benchmark along with a few others in this section really convinced me ram o/c past 1:1, with Conroe, is fairly useless in real world apps.
@Gen - yeah, that's certainly the conclusion I drew from the data. Glad to see people are playing with it.
Test System->>
E2160 M0@3.4 ghz
2x1 GB Twinmos Ddr2 800@1020 @5 5 5 15
---------- RUN1PASS1.LOG
encoded 1442 frames, 36.72 fps, 3905.08 kb/s
---------- RUN2PASS1.LOG
encoded 1442 frames, 36.75 fps, 3905.08 kb/s
---------- RUN3PASS1.LOG
encoded 1442 frames, 36.75 fps, 3905.08 kb/s
---------- RUN4PASS1.LOG
encoded 1442 frames, 36.84 fps, 3905.08 kb/s
---------- RUN1PASS2.LOG
encoded 1442 frames, 9.15 fps, 3942.92 kb/s
---------- RUN2PASS2.LOG
encoded 1442 frames, 9.22 fps, 3942.92 kb/s
---------- RUN3PASS2.LOG
encoded 1442 frames, 9.19 fps, 3942.92 kb/s
---------- RUN4PASS2.LOG
encoded 1442 frames, 9.14 fps, 3942.92 kb/s
the ellusive 4ghz run evaded me this weekend but 3900mhz was pretty stable.
http://aycu32.webshots.com/image/484...4932841_rs.jpg
Code:---------- RUN1PASS1.LOG
encoded 1442 frames, 73.89 fps, 3905.42 kb/s
---------- RUN2PASS1.LOG
encoded 1442 frames, 75.40 fps, 3905.42 kb/s
---------- RUN3PASS1.LOG
encoded 1442 frames, 74.67 fps, 3905.42 kb/s
---------- RUN4PASS1.LOG
encoded 1442 frames, 75.09 fps, 3905.42 kb/s
---------- RUN1PASS2.LOG
encoded 1442 frames, 21.71 fps, 3952.85 kb/s
---------- RUN2PASS2.LOG
encoded 1442 frames, 21.71 fps, 3952.85 kb/s
---------- RUN3PASS2.LOG
encoded 1442 frames, 21.73 fps, 3952.85 kb/s
---------- RUN4PASS2.LOG
encoded 1442 frames, 21.70 fps, 3952.85 kb/s
@Erdemliol - thanks for the data... what is your multiplier and FSB. Also, what O/S and is it 32 or 64 bit?
@Gen - got your new results, thanks... if your first post you said you were running 9x450=3600... is that a typeo? Was it really 9x400=3600 or 9x450=4050?