x264 Benchmark

The x264 benchmark measures how fast your machine can encode a short, DVD quality MPEG-2 video clip into a high-quality x264 video clip.

It will give you results in FPS that can be used to compare the performance of different CPUs and different CPU settings.

Here's a quote from the article :-

​

Link : x264 Benchmark

Official x264 Results : Click to view!

 

1st results

I think this is the first post. i dont have anything to compare my results to so, i do not know how good my results are.


---------- RUN1PASS1.LOG
encoded 1749 frames, 34.96 fps, 1854.10 kb/s

---------- RUN2PASS1.LOG
encoded 1749 frames, 34.99 fps, 1854.10 kb/s

---------- RUN3PASS1.LOG
encoded 1749 frames, 34.73 fps, 1854.10 kb/s

---------- RUN4PASS1.LOG
encoded 1749 frames, 34.90 fps, 1854.10 kb/s

---------- RUN5PASS1.LOG
encoded 1749 frames, 34.91 fps, 1854.10 kb/s

---------- RUN1PASS2.LOG
encoded 1749 frames, 8.65 fps, 1825.89 kb/s

---------- RUN2PASS2.LOG
encoded 1749 frames, 8.70 fps, 1825.89 kb/s

---------- RUN3PASS2.LOG
encoded 1749 frames, 8.68 fps, 1825.89 kb/s

---------- RUN4PASS2.LOG
encoded 1749 frames, 8.38 fps, 1825.89 kb/s

---------- RUN5PASS2.LOG
encoded 1749 frames, 8.69 fps, 1825.89 kb/s

 

Here's mine:

---------- RUN1PASS1.LOG

encoded 1749 frames, 28.47 fps, 1850.89 kb/s



---------- RUN2PASS1.LOG

encoded 1749 frames, 28.82 fps, 1850.89 kb/s



---------- RUN3PASS1.LOG

encoded 1749 frames, 28.73 fps, 1850.89 kb/s



---------- RUN4PASS1.LOG

encoded 1749 frames, 29.64 fps, 1850.89 kb/s



---------- RUN5PASS1.LOG

encoded 1749 frames, 29.67 fps, 1850.89 kb/s



---------- RUN1PASS2.LOG

encoded 1749 frames, 7.04 fps, 1826.37 kb/s



---------- RUN2PASS2.LOG

encoded 1749 frames, 7.05 fps, 1826.37 kb/s



---------- RUN3PASS2.LOG

encoded 1749 frames, 7.17 fps, 1826.27 kb/s



---------- RUN4PASS2.LOG

encoded 1749 frames, 7.26 fps, 1826.37 kb/s



---------- RUN5PASS2.LOG

encoded 1749 frames, 7.23 fps, 1826.38 kb/s


Machine is a Gateway S-7125C laptop.

CPU model: U7500
Code name: C2D/Merom 2M, L2 stepping
Total number of cores: 2
CPU settings: 8x133
Core rate (MHz): 1,064
MB chipset: 945GM + 82801GBM
Timings/Frequency 4-4-4-12 @ 533 MHz
OS: WinXP SP2
MeGUI Test Data FPS 1: 29.38
MeGUI Test Data FPS 2: 7.22

Not bad for a little 1.06 GHz unit, beat the 3.0 GHz P4 on the front page

 

Different architectures. Speed is no longer a good measure.

 

Q6600 8x450 3600mhz
RAM 1:1 4-3-3-10
Evga 680i A1
Vista x64


---------- RUN1PASS1.LOG
encoded 1749 frames, 181.71 fps, 1850.95 kb/s

---------- RUN2PASS1.LOG
encoded 1749 frames, 182.61 fps, 1850.94 kb/s

---------- RUN3PASS1.LOG
encoded 1749 frames, 182.00 fps, 1850.94 kb/s

---------- RUN4PASS1.LOG
encoded 1749 frames, 181.70 fps, 1850.94 kb/s

---------- RUN5PASS1.LOG
encoded 1749 frames, 182.30 fps, 1850.94 kb/s

---------- RUN1PASS2.LOG
encoded 1749 frames, 50.55 fps, 1829.26 kb/s

---------- RUN2PASS2.LOG
encoded 1749 frames, 50.53 fps, 1829.14 kb/s

---------- RUN3PASS2.LOG
encoded 1749 frames, 50.48 fps, 1829.15 kb/s

---------- RUN4PASS2.LOG
encoded 1749 frames, 50.52 fps, 1829.12 kb/s

---------- RUN5PASS2.LOG
encoded 1749 frames, 50.48 fps, 1829.53 kb/s

 

@chillinwitchu - thanks for the results... what o/s are you running? Also, the 4000+ is a single core chip, right?

@MNOTDRPHIL and AMV - thanks for the results!

 

REPLY @ GREYSKY

Sorry i forgot my OS. Its Windows XP PRO W/SP2 build 2600.
and yes, that is a single core. it is however OC'd. Stock speed is 2.4GHz.

regards
chillinwitchu

 

Error in package

So I got the benchmark and it failed, after checking I found that although it includes a version of DGDecode.dll and instructions to install it it seems it does not realize there might be more locations where you have DGDecode.dll installed besides avisynth, and neither does it include dgindex.exe so I had to update those too in all incarnations I have (like AutoGK and StaxRip)
Also I think the batch file should also use the path to the x264.exe rather than just using x264.exe, and perhaps the same for tee.exe for completeness.

 

x264 Test

OS: Windows XP Pro-SP2
Processor: Intel Pentium D 945
Code Name: Presler
Overclocked: 17x230.5
Chipset: Intel i955x
Core Speed: 3917.6
Frequencyz: 460.9
FSB;Dram: 1:2
Timings: 5,5,5,15
MeGUI Test Data FPS 1: 59.17 Avg.
MeGUI Test Data FPS 2: 14.77 Avg.


---------- RUN1PASS1.LOG
encoded 1749 frames, 59.07 fps, 1850.89 kb/s

---------- RUN2PASS1.LOG
encoded 1749 frames, 59.26 fps, 1850.89 kb/s

---------- RUN3PASS1.LOG
encoded 1749 frames, 59.07 fps, 1850.89 kb/s

---------- RUN4PASS1.LOG
encoded 1749 frames, 59.23 fps, 1850.89 kb/s

---------- RUN5PASS1.LOG
encoded 1749 frames, 59.22 fps, 1850.89 kb/s

---------- RUN1PASS2.LOG
encoded 1749 frames, 14.79 fps, 1826.37 kb/s

---------- RUN2PASS2.LOG
encoded 1749 frames, 14.76 fps, 1826.37 kb/s

---------- RUN3PASS2.LOG
encoded 1749 frames, 14.76 fps, 1826.37 kb/s

---------- RUN4PASS2.LOG
encoded 1749 frames, 14.75 fps, 1826.38 kb/s

---------- RUN5PASS2.LOG
encoded 1749 frames, 14.78 fps, 1826.37 kb/s

 

@Chai - Win XP SP2 32 or 64bit?

 

Hi Wwhat. As far as I know, the default path for all plugins for avisynth is its %instaldir%/plugins so unless one has a line in the avs that says otherwise, it should assume that. An example of a non-standard one might be:

Code:

LoadPlugin("F:\AviSynth\plugins\plugin-xyz.dll")

Also, dgindex.exe isn't required for the test. As to the paths in the batch file. I opted to place the exes in the /test dir just to keep the root of the test clean, although doing as you suggested should work just fine as well.

My curiosity is why it doesn't run on your machine. Where did you install your avisynth? If you drag-and-drop the test avs (located in c:\work2\test) into mplayerc, what does it show as an error message (can you post a screenshot of that)?

 

Cool, thanks for the data... do we have any Tech ARP members who are good with asp (I think you guys are using it) so we can bring the data out of a gif file and into a sortible table on the page? You know something akin to the Tom's hardware VGA charts... anyone?

 

Hi

My oced C2D 6400 @3000mhz:

CPU model: Core 2 Duo 6400
Code name: Allendale, B2 stepping
Total number of cores: 2
CPU settings: 8x375
Core rate (MHz): 3000
MB chipset: Intel P965
Timings/Frequency 4-4-4-12 @ 800 MHz (375 mhz)
OS: Vista x64
MeGUI Test Data FPS 1: 84.00 Avg.
MeGUI Test Data FPS 2: 20.86 Avg.

Code:

---------- RUN1PASS1.LOG
encoded 1749 frames, 83.67 fps, 1850.89 kb/s

---------- RUN2PASS1.LOG
encoded 1749 frames, 83.29 fps, 1850.89 kb/s

---------- RUN3PASS1.LOG
encoded 1749 frames, 83.86 fps, 1850.89 kb/s

---------- RUN4PASS1.LOG
encoded 1749 frames, 84.17 fps, 1850.89 kb/s

---------- RUN5PASS1.LOG
encoded 1749 frames, 83.98 fps, 1850.89 kb/s

---------- RUN1PASS2.LOG
encoded 1749 frames, 20.85 fps, 1826.38 kb/s

---------- RUN2PASS2.LOG
encoded 1749 frames, 20.85 fps, 1826.38 kb/s

---------- RUN3PASS2.LOG
encoded 1749 frames, 20.87 fps, 1826.38 kb/s

---------- RUN4PASS2.LOG
encoded 1749 frames, 20.81 fps, 1826.33 kb/s

---------- RUN5PASS2.LOG
encoded 1749 frames, 20.80 fps, 1826.37 kb/s

Click to enlarge

 

And my stock A64 X2 6000+ @3000mhz:

CPU model: Athlon 64 X2 6000+
Code name: Windsor, F3 stepping
Total number of cores: 2
CPU settings: 15x200
Core rate (MHz): 3000
MB chipset: AMD 580X
Timings/Frequency 4-4-4-12 @ 800 MHz (375 mhz)
OS: Vista x64
MeGUI Test Data FPS 1: 80.35 Avg.
MeGUI Test Data FPS 2: 19.68 Avg.

Code:

---------- RUN1PASS1.LOG
encoded 1749 frames, 78.95 fps, 1850.89 kb/s

---------- RUN2PASS1.LOG
encoded 1749 frames, 78.46 fps, 1850.89 kb/s

---------- RUN3PASS1.LOG
encoded 1749 frames, 80.20 fps, 1850.89 kb/s

---------- RUN4PASS1.LOG
encoded 1749 frames, 80.54 fps, 1850.89 kb/s

---------- RUN5PASS1.LOG
encoded 1749 frames, 80.31 fps, 1850.89 kb/s

---------- RUN1PASS2.LOG
encoded 1749 frames, 19.68 fps, 1826.37 kb/s

---------- RUN2PASS2.LOG
encoded 1749 frames, 19.51 fps, 1826.37 kb/s

---------- RUN3PASS2.LOG
encoded 1749 frames, 19.63 fps, 1826.37 kb/s

---------- RUN4PASS2.LOG
encoded 1749 frames, 19.62 fps, 1826.37 kb/s

---------- RUN5PASS2.LOG
encoded 1749 frames, 19.73 fps, 1826.37 kb/s

Click to enlarge

 

Here is another benchmark

---------- RUN1PASS1.LOG
encoded 1749 frames, 67.20 fps, 1850.89 kb/s

---------- RUN2PASS1.LOG
encoded 1749 frames, 65.37 fps, 1850.89 kb/s

---------- RUN3PASS1.LOG
encoded 1749 frames, 68.20 fps, 1850.89 kb/s

---------- RUN4PASS1.LOG
encoded 1749 frames, 66.39 fps, 1850.89 kb/s

---------- RUN5PASS1.LOG
encoded 1749 frames, 68.20 fps, 1850.89 kb/s

---------- RUN1PASS2.LOG
encoded 1749 frames, 17.48 fps, 1826.37 kb/s

---------- RUN2PASS2.LOG
encoded 1749 frames, 17.57 fps, 1826.37 kb/s

---------- RUN3PASS2.LOG
encoded 1749 frames, 17.54 fps, 1826.38 kb/s

---------- RUN4PASS2.LOG
encoded 1749 frames, 17.80 fps, 1826.37 kb/s

---------- RUN5PASS2.LOG
encoded 1749 frames, 17.68 fps, 1826.38 kb/s

core 2d e6700
core 3200.2MHz
multiplier x10
FSB 10
nvidia 650i /570 asus p5n32-e sli plus
4-4-4-12 mem 400MHz
Vista Ultimate 32 bit

 

Core 2 Duo E6850 @ 434x9
Abit IP35 Pro
WinXP SP2 32-bit

---------- RUN1PASS1.LOG
encoded 1749 frames, 105.60 fps, 1850.89 kb/s

---------- RUN2PASS1.LOG
encoded 1749 frames, 108.36 fps, 1850.89 kb/s

---------- RUN3PASS1.LOG
encoded 1749 frames, 108.57 fps, 1850.89 kb/s

---------- RUN4PASS1.LOG
encoded 1749 frames, 108.78 fps, 1850.89 kb/s

---------- RUN5PASS1.LOG
encoded 1749 frames, 108.57 fps, 1850.89 kb/s

---------- RUN1PASS2.LOG
encoded 1749 frames, 26.65 fps, 1826.38 kb/s

---------- RUN2PASS2.LOG
encoded 1749 frames, 27.16 fps, 1826.37 kb/s

---------- RUN3PASS2.LOG
encoded 1749 frames, 27.11 fps, 1826.38 kb/s

---------- RUN4PASS2.LOG
encoded 1749 frames, 27.14 fps, 1826.38 kb/s

---------- RUN5PASS2.LOG
encoded 1749 frames, 27.20 fps, 1826.37 kb/s