x264 Benchmark

Discussion in 'Reviews & Articles' started by Dashken, Sep 9, 2007.

  1. chong

    chong Newbie

    Athlon 64 X2 3600+, Brisbane
    9 x 300MHz
    nForce 570 SLI
    5-5-5-15 @ 450MHz
    XP Pro SP2

    Click: [​IMG]

     
  2. graysky

    graysky ARP Reviewer

    Thanks for the results... what is your mem timings and mem clock rate?
    @chong - thanks!
     
  3. Wwhat

    Wwhat Newbie

    Reply on errorreport

    Well I got a 'dib is an unknown option' or something like that as error and a 'test-480p.avs cannot be opened' (although it was there) on each line and then an empty results file with only the 'log' messages.
    I can't recall the exact verbatim 'dib' error message because I fixed it already before you asked.
    Anyway, So I tried to run the .avs in media player classic as I do normally with avs files and it showed me the error "dgdecode.dll is an incompatible version for dgindex.exe"
    So I downloaded the latest dgmpgdec149 package and installed dgdecode.dll and dgindex.exe from that to the folders StaxRip and AutoGK use, and just the dgdecode.dll to the avisynth plugins folder, and then the bench worked fine.

    What I mean about the folders for the dgdecode.dll is that if you have more than one program that installs dgdecode, in their own respective folder (in whatever version available since you last updated or installed it), like staxrip and autoGK etcetera as done by the GUI for x264 I think it was, then there might be confusion for windows in what to use I'm assuming, because just copying the included dgdecode.dll to only the avisynth plugins folder made it fail, as well as restoring the old version.
    Only after I updated all instances for the various programs it worked without errors.

    And yes I had avisynth installed in its default location and put work2 in c: as instructed and expected by the batch file.
    And plugins I in the past installed manually to the plugins folder of avisynth work as expected with my own .avs creations, so avisynth seems correctly installed.

    Hope this experience helps you guys to tweak the test package.
     
    Last edited: Sep 10, 2007
  4. IMNOTDRPHIL

    IMNOTDRPHIL Newbie

    Oh, I know that. The impressive part is that the U7500 is something over 10x as efficient per watt than the P4 530 is as well as faster overall, and the 530 is only about two years older than the U7500. Goes to show how much NetBurst sucked.
     
  5. wuemura

    wuemura Newbie

    CPU model: Athlon 64 X2 6000+
    Code name: Windsor, F3 stepping
    Total number of cores: 2
    CPU settings: 15x333
    Core rate (MHz): 3000
    MB chipset: nForce4
    Timings/Frequency 5-5-5-15-21 @ 667 MHz (335 Mhz)
    OS: Windows 2003 SP2 (32Bit)

    Code:
    ---------- RUN1PASS1.LOG
    encoded 1749 frames, 69.83 fps, 1850.89 kb/s
    
    ---------- RUN2PASS1.LOG
    encoded 1749 frames, 69.53 fps, 1850.89 kb/s
    
    ---------- RUN3PASS1.LOG
    encoded 1749 frames, 69.65 fps, 1850.89 kb/s
    
    ---------- RUN4PASS1.LOG
    encoded 1749 frames, 69.87 fps, 1850.89 kb/s
    
    ---------- RUN5PASS1.LOG
    encoded 1749 frames, 69.52 fps, 1850.89 kb/s
    
    ---------- RUN1PASS2.LOG
    encoded 1749 frames, 17.99 fps, 1826.38 kb/s
    
    ---------- RUN2PASS2.LOG
    encoded 1749 frames, 17.89 fps, 1826.37 kb/s
    
    ---------- RUN3PASS2.LOG
    encoded 1749 frames, 17.98 fps, 1826.37 kb/s
    
    ---------- RUN4PASS2.LOG
    encoded 1749 frames, 18.00 fps, 1826.37 kb/s
    
    ---------- RUN5PASS2.LOG
    encoded 1749 frames, 17.99 fps, 1826.37 kb/s
    [​IMG][​IMG][​IMG]
     
    Last edited: Sep 10, 2007
  6. Adrian Wong

    Adrian Wong Da Boss Staff Member

    Oh, okay. Just one more thing. What operating system did you use it on? Thanks! :thumb:
     
  7. Chago

    Chago Newbie

    Here are my results:

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

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

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

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

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

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

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

    ---------- RUN3PASS2.LOG
    encoded 1749 frames, 14.46 fps, 1826.33 kb/s

    ---------- RUN4PASS2.LOG
    encoded 1749 frames, 14.46 fps, 1826.27 kb/s

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

    Processor:
    Name AMD Opteron 165 X2 (UP)
    Codename Toledo

    Clocks:
    Core Speed 2478.2 MHz
    Multiplier x 9.0
    Bus Speed 275.4

    Mainboard:
    Chipset NVIDIA GeForce 6100

    Memory:
    Frequency 177.0MHz
    FSB: DRAM CPU/14
    CAS# Latency 2.0 Clocks
    RAS# to CAS# Delay 3 Clocks
    RAS# Precharge 2 Clocks
    Cycle Time (Tras) 5 Clocks
     
  8. Chago

    Chago Newbie

    Sorry guys . . . forgot the OS, XP Pro SP2 . . .
     
  9. Emmett

    Emmett Newbie

    Q6600 GO at 8*473 3.8 gig
    Memory 1183 at 5-5-5-15 timings
    Windows XP SP2 Edit: 32 bit


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

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

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

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

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

    ---------- RUN1PASS2.LOG
    encoded 1749 frames, 53.82 fps, 1829.19 kb/s

    ---------- RUN2PASS2.LOG
    encoded 1749 frames, 53.69 fps, 1829.34 kb/s

    ---------- RUN3PASS2.LOG
    encoded 1749 frames, 54.10 fps, 1829.39 kb/s

    ---------- RUN4PASS2.LOG
    encoded 1749 frames, 54.00 fps, 1829.19 kb/s

    ---------- RUN5PASS2.LOG
    encoded 1749 frames, 53.92 fps, 1829.52 kb/s


    Emmett
     
    Last edited: Sep 10, 2007
  10. davestaple

    davestaple Newbie

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

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

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

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

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

    ---------- RUN1PASS2.LOG
    encoded 1749 frames, 18.17 fps, 1826.21 kb/s

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

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

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

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


    AMD Athlon 64 X2 Brisbane 3600+

    CPU Speed: 295x9.5=2802.5
    Memory Speed: 467Mhz (5-5-5-15)
    nForce 570SLI
    Gigabyte M57SLI-DS4
    WinXP SP2
     
  11. graysky

    graysky ARP Reviewer

    thanks for the data, all

    @emmet - what chipset is your mb using and is your ram really running @ 1183 MHz (2.5x the CPU)?

    @chago - same question about chipsets for you.
     
  12. Chai

    Chai Administrator Staff Member

    Eh, I just noticed a big mistake on my CPU-Z. It was on Speedstep mode. The actual CPU speed is 3.9GHz, 9x multiplier, 435MHz FSB.
     
    Last edited: Sep 11, 2007
  13. Emmett

    Emmett Newbie

    P5K Deluxe...

    P35 based

    Memory was on divider, running 1183 total speed.

    I tried to run it again after that run, and system rebooted..

    Not totally stable, but it ran once :)
     
  14. graysky

    graysky ARP Reviewer

    @Chai - fixed will report later today
    @Emmett - thanks for the info. Again, fixed and will repost later today
     
  15. ditche

    ditche Newbie

    Aloha,

    [​IMG] [​IMG] [​IMG]
    OS : Windows XP Pro SP2

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

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

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

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

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

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

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

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

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

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


    And a little graph... :)

    [​IMG]

    * = CPU o/c
     
    Last edited: Sep 12, 2007
  16. Adrian Wong

    Adrian Wong Da Boss Staff Member

    Very nice graph! :thumb:
     
  17. graysky

    graysky ARP Reviewer

    @ditche - thanks for the data! I was wondering how long it would take before we saw one of your bar graphs :)
     
  18. AMV

    AMV Newbie

    nice job on graph :clap:
     
  19. ditche

    ditche Newbie

    [​IMG] :mrgreen:
    Yes, it's easier to see the differences between all CPU's. :)

    Now, the results with my fantastic Pentium M...
    It's too slow, so there is only 2 runs. :oops:
    Windows Vista Ultimate 32 bits.

    [​IMG]

    [​IMG] [​IMG] [​IMG]
     
  20. Lee2

    Lee2 Newbie

    Hello,
    This is a very nice benchmark to use, fast and easy :thumb: .

    Athlon 64 X2 5000+ Brisbane at standard clock (2,6122 Ghz)
    NForce 570 SLI
    Asus M2N-SLI Deluxe bios revision 0903 dated 13 feb 2007.
    2X1GB DDR2-800 Ram 4-4-4-12 2T command rate@373Mhz.
    Win XP Pro SP2.

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

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

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

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

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

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

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

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

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

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

Share This Page