new HD x264 video encoding benchmark
Moderators: NeilBlanchard, Ralf Hutter, sthayashi, Lawrence Lee
new HD x264 video encoding benchmark
Techarp is hosting a new HD x264 benchmark. Have a look and run it on your system to help populate the data table.
Basically, you run the test encode of an HD sample (1280x720) and it will report back frames-per-second values for your machine @ it's clock/overclock level. You can run it at your stock settings and at your overclock settings to see how your machine compares to others in the database.
My goal is to have a representative set of data for many different chips and chipsets. Please just report your results here in this thread. I will keep the data at that url to keep things simple.
Thanks all and enjoy!
The following image will be updated automatically as new data comes in. It doesn't display any results, but it does show the number of data points collected so far and how they break down by CPU type:
Basically, you run the test encode of an HD sample (1280x720) and it will report back frames-per-second values for your machine @ it's clock/overclock level. You can run it at your stock settings and at your overclock settings to see how your machine compares to others in the database.
My goal is to have a representative set of data for many different chips and chipsets. Please just report your results here in this thread. I will keep the data at that url to keep things simple.
Thanks all and enjoy!
The following image will be updated automatically as new data comes in. It doesn't display any results, but it does show the number of data points collected so far and how they break down by CPU type:
Last edited by graysky on Tue Mar 18, 2008 12:26 pm, edited 1 time in total.
Done
E4500 (stock 11*200)
G33 chipset
2GB DDR2 RAM @ 400MHz 4-4-4-12
Win XP pro SP2 (build 2600)
Let me know if you want more info.
E4500 (stock 11*200)
G33 chipset
2GB DDR2 RAM @ 400MHz 4-4-4-12
Win XP pro SP2 (build 2600)
Code: Select all
---------- RUN1PASS1.LOG
encoded 1442 frames, 24.22 fps, 3905.08 kb/s
---------- RUN2PASS1.LOG
encoded 1442 frames, 24.14 fps, 3905.08 kb/s
---------- RUN3PASS1.LOG
encoded 1442 frames, 24.24 fps, 3905.08 kb/s
---------- RUN4PASS1.LOG
encoded 1442 frames, 24.22 fps, 3905.08 kb/s
---------- RUN1PASS2.LOG
encoded 1442 frames, 6.16 fps, 3942.92 kb/s
---------- RUN2PASS2.LOG
encoded 1442 frames, 6.18 fps, 3942.92 kb/s
---------- RUN3PASS2.LOG
encoded 1442 frames, 6.18 fps, 3942.92 kb/s
---------- RUN4PASS2.LOG
encoded 1442 frames, 6.16 fps, 3942.92 kb/s
-
- Posts: 3142
- Joined: Mon Feb 26, 2007 9:20 am
- Location: Missing in Finnish wilderness, howling to moon with wolf brethren and walking with brother bears
- Contact:
AMD X2 4000+
Core Speed: 2100,4 Mhz
Multiplier: 10,5x
Buss Speed: 200 Mhz
HyperTransport: 1000 Mhz
Chipset: Ati: RS690
Memory: DDR2 2 x 1 GB
Frequency: 200.0 Mhz
Clocks: 5-5-5-15
XP Pro SP2
Core Speed: 2100,4 Mhz
Multiplier: 10,5x
Buss Speed: 200 Mhz
HyperTransport: 1000 Mhz
Chipset: Ati: RS690
Memory: DDR2 2 x 1 GB
Frequency: 200.0 Mhz
Clocks: 5-5-5-15
XP Pro SP2
Code: Select all
---------- RUN1PASS1.LOG
encoded 1442 frames, 21.14 fps, 3905.08 kb/s
---------- RUN2PASS1.LOG
encoded 1442 frames, 21.23 fps, 3905.08 kb/s
---------- RUN3PASS1.LOG
encoded 1442 frames, 21.24 fps, 3905.08 kb/s
---------- RUN4PASS1.LOG
encoded 1442 frames, 21.26 fps, 3905.08 kb/s
---------- RUN1PASS2.LOG
encoded 1442 frames, 4.81 fps, 3942.92 kb/s
---------- RUN2PASS2.LOG
encoded 1442 frames, 4.83 fps, 3942.92 kb/s
---------- RUN3PASS2.LOG
encoded 1442 frames, 4.81 fps, 3942.92 kb/s
---------- RUN4PASS2.LOG
encoded 1442 frames, 4.82 fps, 3942.92 kb/s
I can answer for him: It's a 65nm Brisbane core, as it has a 10.5 multiplier.graysky wrote:@thejamppa - is your 4000+ a Clawhammer (130 nm) or San Diego (90 nm). If you're unsure, CPU-Z will tell you on the first tab.
-
- Posts: 3142
- Joined: Mon Feb 26, 2007 9:20 am
- Location: Missing in Finnish wilderness, howling to moon with wolf brethren and walking with brother bears
- Contact:
Exactly, its Brisbane. Thanks Mikael ^^Mikael wrote:I can answer for him: It's a 65nm Brisbane core, as it has a 10.5 multiplier.graysky wrote:@thejamppa - is your 4000+ a Clawhammer (130 nm) or San Diego (90 nm). If you're unsure, CPU-Z will tell you on the first tab.
E8400 (@3.6GHz, 9*400)
P35 chipset
2GB DDR2, 5-5-5-15 @ 400MHz
XP pro SP x32
P35 chipset
2GB DDR2, 5-5-5-15 @ 400MHz
XP pro SP x32
Code: Select all
---------- RUN1PASS1.LOG
encoded 1442 frames, 39.92 fps, 3905.08 kb/s
---------- RUN2PASS1.LOG
encoded 1442 frames, 40.21 fps, 3905.08 kb/s
---------- RUN3PASS1.LOG
encoded 1442 frames, 40.23 fps, 3905.08 kb/s
---------- RUN4PASS1.LOG
encoded 1442 frames, 40.23 fps, 3905.08 kb/s
---------- RUN1PASS2.LOG
encoded 1442 frames, 10.58 fps, 3942.92 kb/s
---------- RUN2PASS2.LOG
encoded 1442 frames, 10.57 fps, 3942.92 kb/s
---------- RUN3PASS2.LOG
encoded 1442 frames, 10.59 fps, 3942.92 kb/s
---------- RUN4PASS2.LOG
encoded 1442 frames, 10.59 fps, 3942.92 kb/s
here are some results with E4300, IP35Pro, 4GB DDR2-800, vista x64:
2.4GHz(267x9)-890MHz-4-4-4-12-tRD4: average: 25.7675fps, 6.48fps
---------- RUN1PASS1.LOG
encoded 1442 frames, 25.42 fps, 3905.08 kb/s
---------- RUN2PASS1.LOG
encoded 1442 frames, 25.89 fps, 3905.08 kb/s
---------- RUN3PASS1.LOG
encoded 1442 frames, 25.87 fps, 3905.08 kb/s
---------- RUN4PASS1.LOG
encoded 1442 frames, 25.89 fps, 3905.08 kb/s
---------- RUN1PASS2.LOG
encoded 1442 frames, 6.50 fps, 3942.92 kb/s
---------- RUN2PASS2.LOG
encoded 1442 frames, 6.50 fps, 3942.92 kb/s
---------- RUN3PASS2.LOG
encoded 1442 frames, 6.43 fps, 3942.92 kb/s
---------- RUN4PASS2.LOG
encoded 1442 frames, 6.49 fps, 3942.92 kb/s
2.4GHz-890MHz-4-4-4-12-tRD6: average: 25.7675, 6.4675
---------- RUN1PASS1.LOG
encoded 1442 frames, 25.51 fps, 3905.08 kb/s
---------- RUN2PASS1.LOG
encoded 1442 frames, 25.94 fps, 3905.08 kb/s
---------- RUN3PASS1.LOG
encoded 1442 frames, 25.86 fps, 3905.08 kb/s
---------- RUN4PASS1.LOG
encoded 1442 frames, 25.76 fps, 3905.08 kb/s
---------- RUN1PASS2.LOG
encoded 1442 frames, 6.49 fps, 3942.92 kb/s
---------- RUN2PASS2.LOG
encoded 1442 frames, 6.43 fps, 3942.92 kb/s
---------- RUN3PASS2.LOG
encoded 1442 frames, 6.44 fps, 3942.92 kb/s
---------- RUN4PASS2.LOG
encoded 1442 frames, 6.51 fps, 3942.92 kb/s
2.4GHz-890MHz-5-5-5-15-tRD4: average: 25.5625, 6.4375
---------- RUN1PASS1.LOG
encoded 1442 frames, 25.56 fps, 3905.08 kb/s
---------- RUN2PASS1.LOG
encoded 1442 frames, 25.59 fps, 3905.08 kb/s
---------- RUN3PASS1.LOG
encoded 1442 frames, 25.61 fps, 3905.08 kb/s
---------- RUN4PASS1.LOG
encoded 1442 frames, 25.49 fps, 3905.08 kb/s
---------- RUN1PASS2.LOG
encoded 1442 frames, 6.46 fps, 3942.92 kb/s
---------- RUN2PASS2.LOG
encoded 1442 frames, 6.43 fps, 3942.92 kb/s
---------- RUN3PASS2.LOG
encoded 1442 frames, 6.44 fps, 3942.92 kb/s
---------- RUN4PASS2.LOG
encoded 1442 frames, 6.42 fps, 3942.92 kb/s
2.4GHz-1068MHz-5-5-5-15-tRD6: average: 25.8445, 6.50
---------- RUN1PASS1.LOG
encoded 1442 frames, 25.69 fps, 3905.08 kb/s
---------- RUN2PASS1.LOG
encoded 1442 frames, 25.97 fps, 3905.08 kb/s
---------- RUN3PASS1.LOG
encoded 1442 frames, 25.90 fps, 3905.08 kb/s
---------- RUN4PASS1.LOG
encoded 1442 frames, 25.82 fps, 3905.08 kb/s
---------- RUN1PASS2.LOG
encoded 1442 frames, 6.51 fps, 3942.92 kb/s
---------- RUN2PASS2.LOG
encoded 1442 frames, 6.50 fps, 3942.92 kb/s
---------- RUN3PASS2.LOG
encoded 1442 frames, 6.48 fps, 3942.92 kb/s
---------- RUN4PASS2.LOG
encoded 1442 frames, 6.51 fps, 3942.92 kb/s
2.8GHz(9x312)-936MHz-4-4-4-12-tRD4: average: 29.675, 7.5175
---------- RUN1PASS1.LOG
encoded 1442 frames, 29.68 fps, 3905.08 kb/s
---------- RUN2PASS1.LOG
encoded 1442 frames, 29.81 fps, 3905.08 kb/s
---------- RUN3PASS1.LOG
encoded 1442 frames, 29.36 fps, 3905.08 kb/s
---------- RUN4PASS1.LOG
encoded 1442 frames, 29.85 fps, 3905.08 kb/s
---------- RUN1PASS2.LOG
encoded 1442 frames, 7.55 fps, 3942.92 kb/s
---------- RUN2PASS2.LOG
encoded 1442 frames, 7.46 fps, 3942.92 kb/s
---------- RUN3PASS2.LOG
encoded 1442 frames, 7.50 fps, 3942.92 kb/s
---------- RUN4PASS2.LOG
encoded 1442 frames, 7.56 fps, 3942.92 kb/s
I'm pretty confused, surprised with the effect of tRD. It seems that the RAM frequency has an important impact than the DDR2 latendies and tRD (MCH) latency is the last... It seems i would keep 2.8-3.0GHz 1066MHz-5-5-5-15-tRD4-5.
2.4GHz(267x9)-890MHz-4-4-4-12-tRD4: average: 25.7675fps, 6.48fps
---------- RUN1PASS1.LOG
encoded 1442 frames, 25.42 fps, 3905.08 kb/s
---------- RUN2PASS1.LOG
encoded 1442 frames, 25.89 fps, 3905.08 kb/s
---------- RUN3PASS1.LOG
encoded 1442 frames, 25.87 fps, 3905.08 kb/s
---------- RUN4PASS1.LOG
encoded 1442 frames, 25.89 fps, 3905.08 kb/s
---------- RUN1PASS2.LOG
encoded 1442 frames, 6.50 fps, 3942.92 kb/s
---------- RUN2PASS2.LOG
encoded 1442 frames, 6.50 fps, 3942.92 kb/s
---------- RUN3PASS2.LOG
encoded 1442 frames, 6.43 fps, 3942.92 kb/s
---------- RUN4PASS2.LOG
encoded 1442 frames, 6.49 fps, 3942.92 kb/s
2.4GHz-890MHz-4-4-4-12-tRD6: average: 25.7675, 6.4675
---------- RUN1PASS1.LOG
encoded 1442 frames, 25.51 fps, 3905.08 kb/s
---------- RUN2PASS1.LOG
encoded 1442 frames, 25.94 fps, 3905.08 kb/s
---------- RUN3PASS1.LOG
encoded 1442 frames, 25.86 fps, 3905.08 kb/s
---------- RUN4PASS1.LOG
encoded 1442 frames, 25.76 fps, 3905.08 kb/s
---------- RUN1PASS2.LOG
encoded 1442 frames, 6.49 fps, 3942.92 kb/s
---------- RUN2PASS2.LOG
encoded 1442 frames, 6.43 fps, 3942.92 kb/s
---------- RUN3PASS2.LOG
encoded 1442 frames, 6.44 fps, 3942.92 kb/s
---------- RUN4PASS2.LOG
encoded 1442 frames, 6.51 fps, 3942.92 kb/s
2.4GHz-890MHz-5-5-5-15-tRD4: average: 25.5625, 6.4375
---------- RUN1PASS1.LOG
encoded 1442 frames, 25.56 fps, 3905.08 kb/s
---------- RUN2PASS1.LOG
encoded 1442 frames, 25.59 fps, 3905.08 kb/s
---------- RUN3PASS1.LOG
encoded 1442 frames, 25.61 fps, 3905.08 kb/s
---------- RUN4PASS1.LOG
encoded 1442 frames, 25.49 fps, 3905.08 kb/s
---------- RUN1PASS2.LOG
encoded 1442 frames, 6.46 fps, 3942.92 kb/s
---------- RUN2PASS2.LOG
encoded 1442 frames, 6.43 fps, 3942.92 kb/s
---------- RUN3PASS2.LOG
encoded 1442 frames, 6.44 fps, 3942.92 kb/s
---------- RUN4PASS2.LOG
encoded 1442 frames, 6.42 fps, 3942.92 kb/s
2.4GHz-1068MHz-5-5-5-15-tRD6: average: 25.8445, 6.50
---------- RUN1PASS1.LOG
encoded 1442 frames, 25.69 fps, 3905.08 kb/s
---------- RUN2PASS1.LOG
encoded 1442 frames, 25.97 fps, 3905.08 kb/s
---------- RUN3PASS1.LOG
encoded 1442 frames, 25.90 fps, 3905.08 kb/s
---------- RUN4PASS1.LOG
encoded 1442 frames, 25.82 fps, 3905.08 kb/s
---------- RUN1PASS2.LOG
encoded 1442 frames, 6.51 fps, 3942.92 kb/s
---------- RUN2PASS2.LOG
encoded 1442 frames, 6.50 fps, 3942.92 kb/s
---------- RUN3PASS2.LOG
encoded 1442 frames, 6.48 fps, 3942.92 kb/s
---------- RUN4PASS2.LOG
encoded 1442 frames, 6.51 fps, 3942.92 kb/s
2.8GHz(9x312)-936MHz-4-4-4-12-tRD4: average: 29.675, 7.5175
---------- RUN1PASS1.LOG
encoded 1442 frames, 29.68 fps, 3905.08 kb/s
---------- RUN2PASS1.LOG
encoded 1442 frames, 29.81 fps, 3905.08 kb/s
---------- RUN3PASS1.LOG
encoded 1442 frames, 29.36 fps, 3905.08 kb/s
---------- RUN4PASS1.LOG
encoded 1442 frames, 29.85 fps, 3905.08 kb/s
---------- RUN1PASS2.LOG
encoded 1442 frames, 7.55 fps, 3942.92 kb/s
---------- RUN2PASS2.LOG
encoded 1442 frames, 7.46 fps, 3942.92 kb/s
---------- RUN3PASS2.LOG
encoded 1442 frames, 7.50 fps, 3942.92 kb/s
---------- RUN4PASS2.LOG
encoded 1442 frames, 7.56 fps, 3942.92 kb/s
I'm pretty confused, surprised with the effect of tRD. It seems that the RAM frequency has an important impact than the DDR2 latendies and tRD (MCH) latency is the last... It seems i would keep 2.8-3.0GHz 1066MHz-5-5-5-15-tRD4-5.
Cpu: E6750 ( 2.66 GHz 8*333 stock )
Mobo: Gigabyte GA-P35-DS3 P35 Chipset
Ram: Corsair 2 GB DDR2 400 5-5-5-18
OS: Vista Ultimate X86
Mobo: Gigabyte GA-P35-DS3 P35 Chipset
Ram: Corsair 2 GB DDR2 400 5-5-5-18
OS: Vista Ultimate X86
Code: Select all
---------- RUN1PASS1.LOG
encoded 1442 frames, 29.94 fps, 3905.08 kb/s
---------- RUN2PASS1.LOG
encoded 1442 frames, 29.91 fps, 3905.08 kb/s
---------- RUN3PASS1.LOG
encoded 1442 frames, 29.91 fps, 3905.08 kb/s
---------- RUN4PASS1.LOG
encoded 1442 frames, 29.89 fps, 3905.08 kb/s
---------- RUN1PASS2.LOG
encoded 1442 frames, 7.57 fps, 3942.92 kb/s
---------- RUN2PASS2.LOG
encoded 1442 frames, 7.57 fps, 3942.92 kb/s
---------- RUN3PASS2.LOG
encoded 1442 frames, 7.58 fps, 3942.92 kb/s
---------- RUN4PASS2.LOG
encoded 1442 frames, 7.56 fps, 3942.92 kb/s
XP Pro
P35 (IP35 Pro)
E6750 8x376=3008MHz
RAM 4GB 5-5-5-15 @376 1:1
---------- RUN1PASS1.LOG
encoded 1442 frames, 32.19 fps, 3905.08 kb/s
---------- RUN2PASS1.LOG
encoded 1442 frames, 32.90 fps, 3905.08 kb/s
---------- RUN3PASS1.LOG
encoded 1442 frames, 32.90 fps, 3905.08 kb/s
---------- RUN4PASS1.LOG
encoded 1442 frames, 32.81 fps, 3905.08 kb/s
---------- RUN1PASS2.LOG
encoded 1442 frames, 8.34 fps, 3942.92 kb/s
---------- RUN2PASS2.LOG
encoded 1442 frames, 8.33 fps, 3942.92 kb/s
---------- RUN3PASS2.LOG
encoded 1442 frames, 8.35 fps, 3942.92 kb/s
---------- RUN4PASS2.LOG
encoded 1442 frames, 8.32 fps, 3942.92 kb/s
P35 (IP35 Pro)
E6750 8x376=3008MHz
RAM 4GB 5-5-5-15 @376 1:1
---------- RUN1PASS1.LOG
encoded 1442 frames, 32.19 fps, 3905.08 kb/s
---------- RUN2PASS1.LOG
encoded 1442 frames, 32.90 fps, 3905.08 kb/s
---------- RUN3PASS1.LOG
encoded 1442 frames, 32.90 fps, 3905.08 kb/s
---------- RUN4PASS1.LOG
encoded 1442 frames, 32.81 fps, 3905.08 kb/s
---------- RUN1PASS2.LOG
encoded 1442 frames, 8.34 fps, 3942.92 kb/s
---------- RUN2PASS2.LOG
encoded 1442 frames, 8.33 fps, 3942.92 kb/s
---------- RUN3PASS2.LOG
encoded 1442 frames, 8.35 fps, 3942.92 kb/s
---------- RUN4PASS2.LOG
encoded 1442 frames, 8.32 fps, 3942.92 kb/s