1. Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

x264 video encoding benchmark

Discussion in 'Overclocking & Cooling' started by graysky, Sep 9, 2007.

  1. graysky

    Joined:
    Jun 11, 2007
    Messages:
    192 (0.07/day)
    Thanks Received:
    81
    I put together a self-contained x264 video encoding benchmark. Techarp kindly agreed to host the file and results at this URL.

    Basically, you run the test encode 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.

    The database is small right now (as of 08-sep), but as you guys report in results, I will populate it. My goal is to have a representative set of data for many different chips and chipsets. Hopefully, we'll get some Penryn and Phenom data when they become available. Also, if anyone out here has some of the high end AMD chips, please contribute. Instructions and the file are at that url.

    Also, please report your results here in this thread. I will keep the data at that url to keep things simple.

    Thanks all.
     
  2. graysky

    Joined:
    Jun 11, 2007
    Messages:
    192 (0.07/day)
    Thanks Received:
    81
    1 week and no takers...?
     
  3. pt

    pt not a suicide-bomber

    Joined:
    Mar 11, 2006
    Messages:
    8,981 (2.77/day)
    Thanks Received:
    208
    Location:
    Portugal
    i got this error :S
    [​IMG]
     
  4. graysky

    Joined:
    Jun 11, 2007
    Messages:
    192 (0.07/day)
    Thanks Received:
    81
    @pt: did you follow the installation instructions? I'm thinking either you're missing avisynth or missing the dgdecode.dll plugin. Have another look at those steps and lemme know :)
     
  5. pt

    pt not a suicide-bomber

    Joined:
    Mar 11, 2006
    Messages:
    8,981 (2.77/day)
    Thanks Received:
    208
    Location:
    Portugal
    it was the dgdecode :p
    put it in bold black ;)
     
  6. pt

    pt not a suicide-bomber

    Joined:
    Mar 11, 2006
    Messages:
    8,981 (2.77/day)
    Thanks Received:
    208
    Location:
    Portugal
    done :)

    [​IMG]
    also put a database link on 1st post
     
  7. oily_17

    oily_17

    Joined:
    Sep 25, 2006
    Messages:
    2,313 (0.76/day)
    Thanks Received:
    670
    Location:
    Norn Iron
    OK,here are my results running at 2.8MHz.Will run it again at 3.0MHz when I reboot.

    [​IMG]



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

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

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

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

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

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

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

    ---------- RUN3PASS2.LOG
    encoded 1749 frames, 18.26 fps, 1826.26 kb/s

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

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


    EDIT:Added CPU-Z chipset and memory images.
     

    Attached Files:

    Last edited: Sep 16, 2007
  8. hat

    hat Enthusiast

    Joined:
    Nov 20, 2006
    Messages:
    17,143 (5.73/day)
    Thanks Received:
    2,169
    Location:
    Ohio
    WOW, a whopping 3MHz!! :p
    you mean GHz :D
     
    Crunching for Team TPU More than 25k PPD
  9. oily_17

    oily_17

    Joined:
    Sep 25, 2006
    Messages:
    2,313 (0.76/day)
    Thanks Received:
    670
    Location:
    Norn Iron

    LOL yeah,toooo much beer here :toast:
     
  10. DOM

    DOM

    Joined:
    May 30, 2006
    Messages:
    7,551 (2.38/day)
    Thanks Received:
    828
    Location:
    TX, USA
    In CPU-Z it show it in MHz :p
     
  11. oily_17

    oily_17

    Joined:
    Sep 25, 2006
    Messages:
    2,313 (0.76/day)
    Thanks Received:
    670
    Location:
    Norn Iron
    Second run at 2948.2MHz ;).Not stable over 3GHz,maybe more juice required.Slightly better but not by much,PT still beating me..


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

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

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

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

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

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

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

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

    ---------- RUN4PASS2.LOG
    encoded 1749 frames, 18.63 fps, 1826.26 kb/s

    ---------- RUN5PASS2.LOG
    encoded 1749 frames, 18.60 fps, 1826.38 kb/s
     
    Last edited: Sep 16, 2007
  12. graysky

    Joined:
    Jun 11, 2007
    Messages:
    192 (0.07/day)
    Thanks Received:
    81
    @oily_17 - thanks for the data... did you change your mem timings for the 3.0 GHz run?
     
  13. oily_17

    oily_17

    Joined:
    Sep 25, 2006
    Messages:
    2,313 (0.76/day)
    Thanks Received:
    670
    Location:
    Norn Iron
    Here are my CPU-Z screenshots for that run.Maybe will give it another go later,see if I can improve any.

    [​IMG] [​IMG]
     
  14. Lekamies New Member

    Joined:
    Dec 16, 2004
    Messages:
    152 (0.04/day)
    Thanks Received:
    0
    ---------- RUN1PASS1.LOG
    encoded 1749 frames, 191.67 fps, 1850.94 kb/s

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

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

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

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

    ---------- RUN1PASS2.LOG
    encoded 1749 frames, 51.07 fps, 1829.51 kb/s

    ---------- RUN2PASS2.LOG
    encoded 1749 frames, 50.97 fps, 1829.11 kb/s

    ---------- RUN3PASS2.LOG
    encoded 1749 frames, 51.02 fps, 1829.53 kb/s

    ---------- RUN4PASS2.LOG
    encoded 1749 frames, 51.00 fps, 1829.43 kb/s

    ---------- RUN5PASS2.LOG
    encoded 1749 frames, 50.90 fps, 1829.40 kb/s

    Core 2 Quad Q6600, 9x400, P35, 4-4-4-12-2T @ 400MHz, XP Pro SP2.
    [​IMG]
     
  15. graysky

    Joined:
    Jun 11, 2007
    Messages:
    192 (0.07/day)
    Thanks Received:
    81
    cool man, thanks for the data
     
  16. giorgos th.

    giorgos th. New Member

    Joined:
    Nov 10, 2005
    Messages:
    1,540 (0.46/day)
    Thanks Received:
    117
    Location:
    Athens - Hellas
    C2D 6850 @ 3800mhz - GSkill HZ @ 1140mhz - 5-5-5-5


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

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

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

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

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

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

    ---------- RUN2PASS2.LOG
    encoded 1749 frames, 26.50 fps, 1826.27 kb/s

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

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

    ---------- RUN5PASS2.LOG
    encoded 1749 frames, 26.46 fps, 1826.38 kb/s
     
  17. graysky

    Joined:
    Jun 11, 2007
    Messages:
    192 (0.07/day)
    Thanks Received:
    81
    @GT - thanks for the results. Is that 8x475 or 9x422? Also, what chipset and is your RAM really 5-5-5-5 @ 1,140 MHz? Also, what O/S are you using?

    Thanks!
     
  18. Lopez0101

    Joined:
    Aug 16, 2007
    Messages:
    769 (0.28/day)
    Thanks Received:
    113
    Location:
    Overseas
    Q6600 @ 3Ghz 9x333 w/ DDR2-1066 @ 5-5-5-18 timings.

    ---------- RUN1PASS1.LOG
    encoded 1749 frames, 160.59 fps, 1850.94 kb/s

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

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

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

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

    ---------- RUN1PASS2.LOG
    encoded 1749 frames, 42.14 fps, 1829.35 kb/s

    ---------- RUN2PASS2.LOG
    encoded 1749 frames, 41.74 fps, 1829.20 kb/s

    ---------- RUN3PASS2.LOG
    encoded 1749 frames, 41.85 fps, 1829.18 kb/s

    ---------- RUN4PASS2.LOG
    encoded 1749 frames, 41.88 fps, 1829.18 kb/s

    ---------- RUN5PASS2.LOG
    encoded 1749 frames, 42.07 fps, 1829.14 kb/s

    I'll do another run with 4-4-4-12 timings. Normally they're at these timings but I was getting some blue screen errors after attempting 1110Mhz at 2.2v so hopefully I didn't mess with the RAM, I'll try 1066 @ 4-4-4-12 again.

    EDIT: So I ran at 533Mhz 4-4-4-12 and it seemed to do worse, but only very slightly, so much so it could just be some random factor.


    ---------- RUN1PASS1.LOG
    encoded 1749 frames, 159.23 fps, 1850.94 kb/s

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

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

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

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

    ---------- RUN1PASS2.LOG
    encoded 1749 frames, 41.49 fps, 1829.54 kb/s

    ---------- RUN2PASS2.LOG
    encoded 1749 frames, 41.57 fps, 1829.38 kb/s

    ---------- RUN3PASS2.LOG
    encoded 1749 frames, 41.53 fps, 1829.36 kb/s

    ---------- RUN4PASS2.LOG
    encoded 1749 frames, 41.63 fps, 1829.10 kb/s

    ---------- RUN5PASS2.LOG
    encoded 1749 frames, 41.61 fps, 1829.24 kb/s


    I also thought it would be fun to test the 1:1 FSB/RAM ratio to see if it was any better, nope, quite worse.
    This was 9x333 @ 333Mhz 4-4-4-12

    ---------- RUN1PASS1.LOG
    encoded 1749 frames, 153.96 fps, 1850.94 kb/s

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

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

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

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

    ---------- RUN1PASS2.LOG
    encoded 1749 frames, 41.40 fps, 1829.08 kb/s

    ---------- RUN2PASS2.LOG
    encoded 1749 frames, 41.53 fps, 1829.41 kb/s

    ---------- RUN3PASS2.LOG
    encoded 1749 frames, 41.37 fps, 1829.54 kb/s

    ---------- RUN4PASS2.LOG
    encoded 1749 frames, 41.37 fps, 1829.15 kb/s

    ---------- RUN5PASS2.LOG
    encoded 1749 frames, 41.30 fps, 1829.20 kb/s
     
    Last edited: Sep 16, 2007
  19. giorgos th.

    giorgos th. New Member

    Joined:
    Nov 10, 2005
    Messages:
    1,540 (0.46/day)
    Thanks Received:
    117
    Location:
    Athens - Hellas
    it is 8x475 on a P35 chipset with my ram really at 1140mhz @ 5-5-5-5 @ 5:6 using Win XP pro sp2.
     
  20. graysky

    Joined:
    Jun 11, 2007
    Messages:
    192 (0.07/day)
    Thanks Received:
    81
    @lopez - thanks for the results... what is the mem core rate for your first test, what chipset, and what o/s are you running?
     
  21. Snipe343

    Snipe343

    Joined:
    Jul 31, 2007
    Messages:
    1,002 (0.37/day)
    Thanks Received:
    34
    ---------- RUN1PASS1.LOG
    encoded 1749 frames, 52.88 fps, 1850.89 kb/s

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

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

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

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

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

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

    ---------- RUN3PASS2.LOG
    encoded 1749 frames, 12.94 fps, 1826.26 kb/s

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

    ---------- RUN5PASS2.LOG
    encoded 1749 frames, 12.89 fps, 1826.37 kb/s
    :)

    At stock 2.1Ghz(10.5x200)
     
  22. Lopez0101

    Joined:
    Aug 16, 2007
    Messages:
    769 (0.28/day)
    Thanks Received:
    113
    Location:
    Overseas
    Haha, sorry I forgot to post that info. The first one is running 533Mhz like the 3rd. I'm running a P35C-DSR3, Q6600 on WinXP Home SP2.
     
  23. Kursah

    Kursah

    Joined:
    Oct 15, 2006
    Messages:
    8,091 (2.67/day)
    Thanks Received:
    1,851
    Location:
    Missoula, MT, USA
    ---------- RUN1PASS1.LOG
    encoded 1749 frames, 100.21 fps, 1850.89 kb/s

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

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

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

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

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

    ---------- RUN2PASS2.LOG
    encoded 1749 frames, 24.27 fps, 1826.26 kb/s

    ---------- RUN3PASS2.LOG
    encoded 1749 frames, 24.30 fps, 1826.39 kb/s

    ---------- RUN4PASS2.LOG
    encoded 1749 frames, 24.29 fps, 1826.26 kb/s

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

    7x500, see System Specs for more info. :toast:
     
  24. DOM

    DOM

    Joined:
    May 30, 2006
    Messages:
    7,551 (2.38/day)
    Thanks Received:
    828
    Location:
    TX, USA
    ---------- RUN1PASS1.LOG
    encoded 1749 frames, 94.54 fps, 1850.89 kb/s

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

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

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

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

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

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

    ---------- RUN3PASS2.LOG
    encoded 1749 frames, 22.71 fps, 1826.26 kb/s

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

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

    Attached Files:

  25. graysky

    Joined:
    Jun 11, 2007
    Messages:
    192 (0.07/day)
    Thanks Received:
    81
    @lopez - actually your 1,066 run vs. your 667 run are identical when you compare the overall time to encode (both 53 seconds). The frames per second values can be a little misleading if taken in a vacuum.
     

Currently Active Users Viewing This Thread: 1 (0 members and 1 guest)

Share This Page