new HD x264 video encoding benchmark

[graysky]

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:

 

[regan1985]

all i get is this???

 

[graysky]

Damn... are you running vista 64 by chance? If so, have a look at your:

c:\Program Files(x86)\AviSynth 2.5

Inside there, is there a directory called "plugins"? If so, does it contain DGDecode.dll at all?

 

[regan1985]

no i am running vista 32 with sp1 beta

but i have looked in that location and no it doesnt contain that file hope this helps

 

[regan1985]

after copying the file into the plugings in AviSynth it worked fine. here is my 1st result on my everyday use
with vista 32 sp1 beta

 

[graysky]

Cool man, thanks for the data.

 

[exodusprime1337]

here's mine

 

[graysky]

Cool man, thanks... what vista flavor is it (32 or 64)?

 

[exodusprime1337]

it's windows xp not vista at all

 

[graysky]

it's windows xp not vista at all

Sorry man, I saw regan1985's screenshot when I asked you that... XP 32-bit or 64-bit?

 

[exodusprime1337]

32 bit buddy

 

[lemonadesoda]

Great to have an easy to use encoding benchmark! Good stuff. BUT

1./ The benchmark is way too thorough... takes much to long to do multiple runs of the same encoding. Quite honestly, this isnt necessary.
2./ The benchmark results are silly. Why report the data density of the media file (ie the kb/s of the media stream)? What should be reported is the ENCODING SPEED.
3./ Just a summary benchmark INDEX would be handy
4./ Wheres the checksum for "honest results" checking?

[quote="ICE-QUAD", Windows 2003 SP2 32-bit, Intel 865PE, FSB 1066, Q6600 @2.4, 2Gb DDR @400, 2-3-3-6, X800SE AGP]
---------- RUN1PASS1.LOG
encoded 1442 frames, 46.10 fps, 3905.42 kb/s

---------- RUN2PASS1.LOG
encoded 1442 frames, 46.10 fps, 3905.42 kb/s

---------- RUN3PASS1.LOG
encoded 1442 frames, 46.03 fps, 3905.42 kb/s

---------- RUN4PASS1.LOG
encoded 1442 frames, 45.85 fps, 3905.42 kb/s

---------- RUN1PASS2.LOG
encoded 1442 frames, 13.61 fps, 3952.85 kb/s

---------- RUN2PASS2.LOG
encoded 1442 frames, 13.62 fps, 3952.85 kb/s

---------- RUN3PASS2.LOG
encoded 1442 frames, 13.63 fps, 3952.85 kb/s

---------- RUN4PASS2.LOG
encoded 1442 frames, 13.60 fps, 3952.85 kb/s[/quote]

P.S. variable results, because I'm browsing whilst this benchmark is running.

LINK http://www.techarp.com/x264_Benchmark/hd/HD_benchmark_results_pub.xls

 

[graysky]

Great to have an easy to use encoding benchmark! Good stuff. BUT

1./ The benchmark is way too thorough... takes much to long to do multiple runs of the same encoding. Quite honestly, this isnt necessary.
2./ The benchmark results are silly. Why report the data density of the media file (ie the kb/s of the media stream)? What should be reported is the ENCODING SPEED.
3./ Just a summary benchmark INDEX would be handy
4./ Wheres the checksum for "honest results" checking?

P.S. variable results, because I'm browsing whilst this benchmark is running.

Can you give me a few more details on your hardware?

It's a q6600 but what is the multiplier and FSB? Also what speed is your memory running and what are the timings? Finally, what chipset is your MB?

Thanks for the input. Let me try to answer your four questions:

1) I wanted multiples for the runs to insure an accurate result. I think an n=3 is just good science.

2) The data density gets reported automatically by x264.exe; I'm not actually using it, just the FPS values for each pass which allows the calculation of the total encoding speed (have a look at the tables on the techarp link).

3) Good idea! I will put something together... what do you think should be kept from the larger tables in an index? CPU, Core Speed, Total Encode Time?

4) I would loved to have incorporated a data integrity check, but sadly, I don't have the programming skills to make it work. I do check the data against itself for like processors and if a data point clearly stands out from the pack, I delete it. I am happy to say that of the over 280 results of my first "SDTV" x264 benchmark (used a 720x480 clip), I only found one such suspect data point.

 

[lemonadesoda]

I'm Q6600 at stock on intel 865PE.

1) I understand the reason... but for the sake of everyones short life... do n=1. People can always re-run if they want a second opinion. Alternatively, make n= user input. But then only report the AVERAGE of the n runs.

2) I see, ok

3) INDEX = total encode time (average if n>1)

4) OK, but you could do a very rudimentary checksum calculation on the INDEX figure.

Otherwise, great work.

PS. I didnt even look at the mpg file... perhaps I'll go that now! LOL

 

[lemonadesoda]

Just looked... oh. Boring. But I did notice the sound was lost on the MP4. Is that deliberate? Does the utility only render the video portion? Or do I have a broken MP4 codec?

 

[VulkanBros]

Here are mine ( Vista 64-bit )

 

[CrAsHnBuRnXp]

Damn... are you running vista 64 by chance? If so, have a look at your:

c:\Program Files(x86)\AviSynth 2.5

Inside there, is there a directory called "plugins"? If so, does it contain DGDecode.dll at all?

Where can I find the DGDecode.dll file to copy into the plugin folder?

 

[VulkanBros]

Here it is

 

[Deleted member 3]

Ran it on the background, CPU load was ~60% during the run.

---------- RUN1PASS1.LOG
encoded 1442 frames, 52.14 fps, 3901.76 kb/s

---------- RUN2PASS1.LOG
encoded 1442 frames, 52.29 fps, 3898.38 kb/s

---------- RUN3PASS1.LOG
encoded 1442 frames, 52.20 fps, 3899.52 kb/s

---------- RUN4PASS1.LOG
encoded 1442 frames, 52.02 fps, 3899.52 kb/s

---------- RUN1PASS2.LOG
encoded 1442 frames, 24.42 fps, 3974.82 kb/s

---------- RUN2PASS2.LOG
encoded 1442 frames, 24.40 fps, 3972.63 kb/s

---------- RUN3PASS2.LOG
encoded 1442 frames, 24.38 fps, 3972.59 kb/s

---------- RUN4PASS2.LOG
encoded 1442 frames, 24.47 fps, 3972.59 kb/s

 

[CrAsHnBuRnXp]

Here it is

But mine isnt in there. Im talking about where I can get the file so I can put it there.

 

[lemonadesoda]

Ooooh, nice Dan. Me also wantie Dual Quad Xeons

Thats a great demo of the power of 8.

WAIT. Somethings wrong. Look at those kb/s numbers. That's the video density. PASS 1 should ALWAYS BE THE SAME (same for PASS2). What's going on? Why is your run giving you different figures? Broken FPU? One of those cores got a math bug?

 

[graysky]

@lemonaidsoda - a few other questions: what is the running speed of your RAM and what o/s are you running (like windows xp 32-bit or 64-bit)?

Just looked... oh. Boring. But I did notice the sound was lost on the MP4. Is that deliberate? Does the utility only render the video portion? Or do I have a broken MP4 codec?

Yeah, since it's a measure of pure video, I did not included an audio track.

 

[graysky]

Where can I find the DGDecode.dll file to copy into the plugin folder?

The dll is in the "test" directory of the benchmark. It should have been automatically copied into your %programfiles%\avisynth 2.5\plugins or if running 64-bit o/s your %programfiles(x86)%\avisynth 2.5\plugins

For some reason this isn't happening on some vista machines. Regan1985's for example, and now your machine. Can you do me a favor to help troubleshoot this?

Please post the full path to the location of your avisynth directory.

 

[graysky]

Here are mine ( Vista 64-bit )

Thanks for the data! Just to be sure I got it right... is your memory running @ 1,066 MHz or just rated at that speed? CPU-Z can tell you (memory tab) what it's running at.

 

[graysky]

Ran it on the background, CPU load was ~60% during the run.

Thanks for the results! Since your clock speed is 2.28 GHz, I guessing you're running @ 6x380? Also, when you said it only ran @ 60 %, was that just for the 1st pass or did the 2nd pass as well only run @ 60 %?