x264 video encoding benchmark
Moderators: NeilBlanchard, Ralf Hutter, sthayashi, Lawrence Lee
x264 video encoding benchmark
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.
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.
Hi, well I've just run the test on my machine clocked as I normally use it. No clean boot or anything, just shut everything down and ran the test.
Core 2 Duo E6600 (2.4GHz, 4MB) @ 3326 (475 x 7), 2x1GB DDR2 950 5,5,5,15 dual channel, Asus P5B-E Plus P965 motherboard. (WD 5000AAKS, ATi X1950pro, etc etc) Vista Home Premium 32bit
Results
---------- RUN1PASS1.LOG
encoded 1749 frames, 92.07 fps, 1850.89 kb/s
---------- RUN2PASS1.LOG
encoded 1749 frames, 91.79 fps, 1850.89 kb/s
---------- RUN3PASS1.LOG
encoded 1749 frames, 92.63 fps, 1850.89 kb/s
---------- RUN4PASS1.LOG
encoded 1749 frames, 92.76 fps, 1850.89 kb/s
---------- RUN5PASS1.LOG
encoded 1749 frames, 92.49 fps, 1850.89 kb/s
---------- RUN1PASS2.LOG
encoded 1749 frames, 22.89 fps, 1826.37 kb/s
---------- RUN2PASS2.LOG
encoded 1749 frames, 22.94 fps, 1826.38 kb/s
---------- RUN3PASS2.LOG
encoded 1749 frames, 22.95 fps, 1826.38 kb/s
---------- RUN4PASS2.LOG
encoded 1749 frames, 22.75 fps, 1826.33 kb/s
---------- RUN5PASS2.LOG
encoded 1749 frames, 22.99 fps, 1826.38 kb/s
Will edit this and add other clockspeeds eventually. Regards, Seb
Core 2 Duo E6600 (2.4GHz, 4MB) @ 3326 (475 x 7), 2x1GB DDR2 950 5,5,5,15 dual channel, Asus P5B-E Plus P965 motherboard. (WD 5000AAKS, ATi X1950pro, etc etc) Vista Home Premium 32bit
Results
---------- RUN1PASS1.LOG
encoded 1749 frames, 92.07 fps, 1850.89 kb/s
---------- RUN2PASS1.LOG
encoded 1749 frames, 91.79 fps, 1850.89 kb/s
---------- RUN3PASS1.LOG
encoded 1749 frames, 92.63 fps, 1850.89 kb/s
---------- RUN4PASS1.LOG
encoded 1749 frames, 92.76 fps, 1850.89 kb/s
---------- RUN5PASS1.LOG
encoded 1749 frames, 92.49 fps, 1850.89 kb/s
---------- RUN1PASS2.LOG
encoded 1749 frames, 22.89 fps, 1826.37 kb/s
---------- RUN2PASS2.LOG
encoded 1749 frames, 22.94 fps, 1826.38 kb/s
---------- RUN3PASS2.LOG
encoded 1749 frames, 22.95 fps, 1826.38 kb/s
---------- RUN4PASS2.LOG
encoded 1749 frames, 22.75 fps, 1826.33 kb/s
---------- RUN5PASS2.LOG
encoded 1749 frames, 22.99 fps, 1826.38 kb/s
Will edit this and add other clockspeeds eventually. Regards, Seb
Thanks for the result. What is your mem clocked @ (like 475 MHz or ...?)SebRad wrote:Core 2 Duo E6600 (2.4GHz, 4MB) @ 3326 (475 x 7), 2x1GB DDR2 950 5,5,5,15 dual channel, Asus P5B-E Plus P965 motherboard. (WD 5000AAKS, ATi X1950pro, etc etc) Vista Home Premium 32bit
Also, would you be willing to run the same benchmark @ stock settings for comparison (9x266)?
I believe if the version you have is older, the avs will not work. What you can do is temporarly rename your current dgindex.dll to dgindex.current and copy the one from the benchmark to the /avisynth/plugins to run the benchmark. When you're finished, simply delete the dgindex.dll from the benchmark and rename your original one back.ACook wrote:what happens if you have a diff version of avs installed? and when I already have a version of dgindex.dll in my avs plugins? no id which version.If you don't have AVISynth 2.5.7 on your machine, you'll need to install it before running the benchmark.
-
- Posts: 419
- Joined: Sun Sep 19, 2004 1:05 pm
- Location: Palo Alto, CA
A64 X2 6000+ Stock Speed, 4x1GB DDR2 800 5-5-5-15, see sig for more details.
Results:
---------- RUN1PASS1.LOG
encoded 1749 frames, 75.25 fps, 1850.89 kb/s
---------- RUN2PASS1.LOG
encoded 1749 frames, 75.21 fps, 1850.89 kb/s
---------- RUN3PASS1.LOG
encoded 1749 frames, 75.57 fps, 1850.89 kb/s
---------- RUN4PASS1.LOG
encoded 1749 frames, 75.50 fps, 1850.89 kb/s
---------- RUN5PASS1.LOG
encoded 1749 frames, 75.22 fps, 1850.89 kb/s
---------- RUN1PASS2.LOG
encoded 1749 frames, 18.58 fps, 1826.37 kb/s
---------- RUN2PASS2.LOG
encoded 1749 frames, 18.58 fps, 1826.38 kb/s
---------- RUN3PASS2.LOG
encoded 1749 frames, 18.63 fps, 1826.37 kb/s
---------- RUN4PASS2.LOG
encoded 1749 frames, 18.70 fps, 1826.38 kb/s
---------- RUN5PASS2.LOG
encoded 1749 frames, 18.67 fps, 1826.38 kb/s
Results:
---------- RUN1PASS1.LOG
encoded 1749 frames, 75.25 fps, 1850.89 kb/s
---------- RUN2PASS1.LOG
encoded 1749 frames, 75.21 fps, 1850.89 kb/s
---------- RUN3PASS1.LOG
encoded 1749 frames, 75.57 fps, 1850.89 kb/s
---------- RUN4PASS1.LOG
encoded 1749 frames, 75.50 fps, 1850.89 kb/s
---------- RUN5PASS1.LOG
encoded 1749 frames, 75.22 fps, 1850.89 kb/s
---------- RUN1PASS2.LOG
encoded 1749 frames, 18.58 fps, 1826.37 kb/s
---------- RUN2PASS2.LOG
encoded 1749 frames, 18.58 fps, 1826.38 kb/s
---------- RUN3PASS2.LOG
encoded 1749 frames, 18.63 fps, 1826.37 kb/s
---------- RUN4PASS2.LOG
encoded 1749 frames, 18.70 fps, 1826.38 kb/s
---------- RUN5PASS2.LOG
encoded 1749 frames, 18.67 fps, 1826.38 kb/s
k, my lowly A64 3000+ winchester, 9x200,9 according to cpuz. so not oc'd.
also, when running this, I had 10 tabs open on opera including irc, and some other programs idling in the bg, while seeding stuff on azureus. can't imagine that having much effect on overall performance though. for the duration of the test I did not increase the speed on the zalman from 25%, and temp didn't go over 51C, which was nice. idle temp is 40. thinking of upgrading to x2 3800 to squeeze another year out of this thing, wonder what that will do to my temps.
edit: full specs:
AMD Athlon 64 3000+ Winchester Socket939, 9 x 200.9MHz, NForce4
mem: 3-3-3-8 1T @ 200.9MHz
think that's all stock.
---------- RUN1PASS1.LOG
encoded 1749 frames, 23.52 fps, 1854.10 kb/s
---------- RUN2PASS1.LOG
encoded 1749 frames, 23.12 fps, 1854.10 kb/s
---------- RUN3PASS1.LOG
encoded 1749 frames, 23.88 fps, 1854.10 kb/s
---------- RUN4PASS1.LOG
encoded 1749 frames, 23.49 fps, 1854.10 kb/s
---------- RUN5PASS1.LOG
encoded 1749 frames, 23.54 fps, 1854.10 kb/s
---------- RUN1PASS2.LOG
encoded 1749 frames, 5.36 fps, 1825.89 kb/s
---------- RUN2PASS2.LOG
encoded 1749 frames, 5.43 fps, 1825.89 kb/s
---------- RUN3PASS2.LOG
encoded 1749 frames, 5.48 fps, 1825.89 kb/s
---------- RUN4PASS2.LOG
encoded 1749 frames, 5.55 fps, 1825.89 kb/s
---------- RUN5PASS2.LOG
encoded 1749 frames, 5.32 fps, 1825.89 kb/s
ps: avs 2.5.6 was installed, didn't change.
also, when running this, I had 10 tabs open on opera including irc, and some other programs idling in the bg, while seeding stuff on azureus. can't imagine that having much effect on overall performance though. for the duration of the test I did not increase the speed on the zalman from 25%, and temp didn't go over 51C, which was nice. idle temp is 40. thinking of upgrading to x2 3800 to squeeze another year out of this thing, wonder what that will do to my temps.
edit: full specs:
AMD Athlon 64 3000+ Winchester Socket939, 9 x 200.9MHz, NForce4
mem: 3-3-3-8 1T @ 200.9MHz
think that's all stock.
---------- RUN1PASS1.LOG
encoded 1749 frames, 23.52 fps, 1854.10 kb/s
---------- RUN2PASS1.LOG
encoded 1749 frames, 23.12 fps, 1854.10 kb/s
---------- RUN3PASS1.LOG
encoded 1749 frames, 23.88 fps, 1854.10 kb/s
---------- RUN4PASS1.LOG
encoded 1749 frames, 23.49 fps, 1854.10 kb/s
---------- RUN5PASS1.LOG
encoded 1749 frames, 23.54 fps, 1854.10 kb/s
---------- RUN1PASS2.LOG
encoded 1749 frames, 5.36 fps, 1825.89 kb/s
---------- RUN2PASS2.LOG
encoded 1749 frames, 5.43 fps, 1825.89 kb/s
---------- RUN3PASS2.LOG
encoded 1749 frames, 5.48 fps, 1825.89 kb/s
---------- RUN4PASS2.LOG
encoded 1749 frames, 5.55 fps, 1825.89 kb/s
---------- RUN5PASS2.LOG
encoded 1749 frames, 5.32 fps, 1825.89 kb/s
ps: avs 2.5.6 was installed, didn't change.
-
- Posts: 312
- Joined: Tue Jul 24, 2007 3:57 pm
- Location: Minnesota
AMD 5600X2, Crucial DDR2-800 4-4-4-12. Nvidia 590 Chipset, Asus board, stock timings.
Seems kinda slow
---------- RUN1PASS1.LOG
encoded 1749 frames, 74.32 fps, 1850.89 kb/s
---------- RUN2PASS1.LOG
encoded 1749 frames, 74.52 fps, 1850.89 kb/s
---------- RUN3PASS1.LOG
encoded 1749 frames, 74.48 fps, 1850.89 kb/s
---------- RUN4PASS1.LOG
encoded 1749 frames, 74.33 fps, 1850.89 kb/s
---------- RUN5PASS1.LOG
encoded 1749 frames, 74.43 fps, 1850.89 kb/s
---------- RUN1PASS2.LOG
encoded 1749 frames, 18.20 fps, 1826.37 kb/s
---------- RUN2PASS2.LOG
encoded 1749 frames, 18.23 fps, 1826.38 kb/s
---------- RUN3PASS2.LOG
encoded 1749 frames, 18.14 fps, 1826.38 kb/s
---------- RUN4PASS2.LOG
encoded 1749 frames, 18.18 fps, 1826.37 kb/s
---------- RUN5PASS2.LOG
encoded 1749 frames, 18.17 fps, 1826.37 kb/s
edit; 4-3-3-10 memory timings
---------- RUN1PASS1.LOG
encoded 1749 frames, 75.17 fps, 1850.89 kb/s
---------- RUN2PASS1.LOG
encoded 1749 frames, 75.33 fps, 1850.89 kb/s
---------- RUN3PASS1.LOG
encoded 1749 frames, 75.28 fps, 1850.89 kb/s
---------- RUN4PASS1.LOG
encoded 1749 frames, 75.23 fps, 1850.89 kb/s
---------- RUN5PASS1.LOG
encoded 1749 frames, 74.77 fps, 1850.89 kb/s
---------- RUN1PASS2.LOG
encoded 1749 frames, 18.35 fps, 1826.38 kb/s
---------- RUN2PASS2.LOG
encoded 1749 frames, 18.40 fps, 1826.38 kb/s
---------- RUN3PASS2.LOG
encoded 1749 frames, 18.40 fps, 1826.37 kb/s
---------- RUN4PASS2.LOG
encoded 1749 frames, 18.40 fps, 1826.37 kb/s
---------- RUN5PASS2.LOG
encoded 1749 frames, 18.43 fps, 1826.37 kb/s
Seems kinda slow
---------- RUN1PASS1.LOG
encoded 1749 frames, 74.32 fps, 1850.89 kb/s
---------- RUN2PASS1.LOG
encoded 1749 frames, 74.52 fps, 1850.89 kb/s
---------- RUN3PASS1.LOG
encoded 1749 frames, 74.48 fps, 1850.89 kb/s
---------- RUN4PASS1.LOG
encoded 1749 frames, 74.33 fps, 1850.89 kb/s
---------- RUN5PASS1.LOG
encoded 1749 frames, 74.43 fps, 1850.89 kb/s
---------- RUN1PASS2.LOG
encoded 1749 frames, 18.20 fps, 1826.37 kb/s
---------- RUN2PASS2.LOG
encoded 1749 frames, 18.23 fps, 1826.38 kb/s
---------- RUN3PASS2.LOG
encoded 1749 frames, 18.14 fps, 1826.38 kb/s
---------- RUN4PASS2.LOG
encoded 1749 frames, 18.18 fps, 1826.37 kb/s
---------- RUN5PASS2.LOG
encoded 1749 frames, 18.17 fps, 1826.37 kb/s
edit; 4-3-3-10 memory timings
---------- RUN1PASS1.LOG
encoded 1749 frames, 75.17 fps, 1850.89 kb/s
---------- RUN2PASS1.LOG
encoded 1749 frames, 75.33 fps, 1850.89 kb/s
---------- RUN3PASS1.LOG
encoded 1749 frames, 75.28 fps, 1850.89 kb/s
---------- RUN4PASS1.LOG
encoded 1749 frames, 75.23 fps, 1850.89 kb/s
---------- RUN5PASS1.LOG
encoded 1749 frames, 74.77 fps, 1850.89 kb/s
---------- RUN1PASS2.LOG
encoded 1749 frames, 18.35 fps, 1826.38 kb/s
---------- RUN2PASS2.LOG
encoded 1749 frames, 18.40 fps, 1826.38 kb/s
---------- RUN3PASS2.LOG
encoded 1749 frames, 18.40 fps, 1826.37 kb/s
---------- RUN4PASS2.LOG
encoded 1749 frames, 18.40 fps, 1826.37 kb/s
---------- RUN5PASS2.LOG
encoded 1749 frames, 18.43 fps, 1826.37 kb/s
Last edited by protellect on Tue Sep 11, 2007 5:03 pm, edited 1 time in total.
Intel Pentium 4 Williamette 1.5Ghz, 15x100, 768MB dual channel RDRAM 400Mhz Timings 11,9. Intel D850GB i850, XP Pro SP2.
---------- RUN1PASS1.LOG
encoded 1749 frames, 9.28 fps, 1854.10 kb/s
---------- RUN2PASS1.LOG
encoded 1749 frames, 9.39 fps, 1854.10 kb/s
---------- RUN3PASS1.LOG
encoded 1749 frames, 9.21 fps, 1854.10 kb/s
---------- RUN4PASS1.LOG
encoded 1749 frames, 9.37 fps, 1854.10 kb/s
---------- RUN5PASS1.LOG
encoded 1749 frames, 9.40 fps, 1854.10 kb/s
---------- RUN1PASS2.LOG
encoded 1749 frames, 2.11 fps, 1825.89 kb/s
---------- RUN2PASS2.LOG
encoded 1749 frames, 2.12 fps, 1825.89 kb/s
---------- RUN3PASS2.LOG
encoded 1749 frames, 2.02 fps, 1825.89 kb/s
---------- RUN4PASS2.LOG
encoded 1749 frames, 2.01 fps, 1825.89 kb/s
---------- RUN5PASS2.LOG
encoded 1749 frames, 2.12 fps, 1825.89 kb/s
PS: Yes, this is my main box. Yes, it belongs in a museum. Yes, I'm going to upgdrade soon.
---------- RUN1PASS1.LOG
encoded 1749 frames, 9.28 fps, 1854.10 kb/s
---------- RUN2PASS1.LOG
encoded 1749 frames, 9.39 fps, 1854.10 kb/s
---------- RUN3PASS1.LOG
encoded 1749 frames, 9.21 fps, 1854.10 kb/s
---------- RUN4PASS1.LOG
encoded 1749 frames, 9.37 fps, 1854.10 kb/s
---------- RUN5PASS1.LOG
encoded 1749 frames, 9.40 fps, 1854.10 kb/s
---------- RUN1PASS2.LOG
encoded 1749 frames, 2.11 fps, 1825.89 kb/s
---------- RUN2PASS2.LOG
encoded 1749 frames, 2.12 fps, 1825.89 kb/s
---------- RUN3PASS2.LOG
encoded 1749 frames, 2.02 fps, 1825.89 kb/s
---------- RUN4PASS2.LOG
encoded 1749 frames, 2.01 fps, 1825.89 kb/s
---------- RUN5PASS2.LOG
encoded 1749 frames, 2.12 fps, 1825.89 kb/s
PS: Yes, this is my main box. Yes, it belongs in a museum. Yes, I'm going to upgdrade soon.
-
- Patron of SPCR
- Posts: 857
- Joined: Fri Dec 27, 2002 1:49 pm
- Location: Somerset, WI - USA
- Contact:
I was really tempted to try this on a new server we just got at work with two Xeon X5355 (8 cores total). If I would have seen this a week earlier I probably could have. I did install Windows Server 2003 on it at first just to get it up and running. But now I've got VMWare and a couple VMs running on it. I can't afford to take it down just for something fun. I did run it on a VM with 4 virtual CPUs. But the results were right at the bottom of the Quad-core CPUs. The Fully Buffered memory and virtual machine overhead probably don't help.
-
- Posts: 20
- Joined: Sat Aug 11, 2007 8:15 am
I fell asleep
...but, the program kept running.
X2 4400, 2 GB DDR400 dual channel, 6150 chipset and XP 32 bit
stock clocked
---------- RUN1PASS1.LOG
encoded 1749 frames, 58.79 fps, 1850.89 kb/s
---------- RUN2PASS1.LOG
encoded 1749 frames, 58.51 fps, 1850.89 kb/s
---------- RUN3PASS1.LOG
encoded 1749 frames, 58.76 fps, 1850.89 kb/s
---------- RUN4PASS1.LOG
encoded 1749 frames, 59.16 fps, 1850.89 kb/s
---------- RUN5PASS1.LOG
encoded 1749 frames, 58.91 fps, 1850.89 kb/s
---------- RUN1PASS2.LOG
encoded 1749 frames, 14.01 fps, 1826.38 kb/s
---------- RUN2PASS2.LOG
encoded 1749 frames, 14.03 fps, 1826.37 kb/s
---------- RUN3PASS2.LOG
encoded 1749 frames, 14.11 fps, 1826.37 kb/s
---------- RUN4PASS2.LOG
encoded 1749 frames, 14.15 fps, 1826.37 kb/s
---------- RUN5PASS2.LOG
encoded 1749 frames, 14.15 fps, 1826.37 kb/s
I did some other things while it was running, but not much. Like I said, I fell asleep.
X2 4400, 2 GB DDR400 dual channel, 6150 chipset and XP 32 bit
stock clocked
---------- RUN1PASS1.LOG
encoded 1749 frames, 58.79 fps, 1850.89 kb/s
---------- RUN2PASS1.LOG
encoded 1749 frames, 58.51 fps, 1850.89 kb/s
---------- RUN3PASS1.LOG
encoded 1749 frames, 58.76 fps, 1850.89 kb/s
---------- RUN4PASS1.LOG
encoded 1749 frames, 59.16 fps, 1850.89 kb/s
---------- RUN5PASS1.LOG
encoded 1749 frames, 58.91 fps, 1850.89 kb/s
---------- RUN1PASS2.LOG
encoded 1749 frames, 14.01 fps, 1826.38 kb/s
---------- RUN2PASS2.LOG
encoded 1749 frames, 14.03 fps, 1826.37 kb/s
---------- RUN3PASS2.LOG
encoded 1749 frames, 14.11 fps, 1826.37 kb/s
---------- RUN4PASS2.LOG
encoded 1749 frames, 14.15 fps, 1826.37 kb/s
---------- RUN5PASS2.LOG
encoded 1749 frames, 14.15 fps, 1826.37 kb/s
I did some other things while it was running, but not much. Like I said, I fell asleep.
-
- Posts: 524
- Joined: Sun Oct 22, 2006 7:39 pm
- Location: Denver, Colorado USA
- Contact:
Re: I fell asleep
Cool man, thanks for the results. Can you report your mem timings and final mem core rate (i.e. 5-5-5-15 @ 400 MHz) Also who makes your motherboard? I never heard of a 6150 chipset.notquitequiet wrote:...but, the program kept running.
X2 4400, 2 GB DDR400 dual channel, 6150 chipset and XP 32 bit
stock clocked
Thanks!
Pentium Dual Core E2160 @ 3.00GHz (9*333)
4GB DDR2-833MHz 5-5-5-15
Asus P5B
Windows XP SP2
---------- RUN1PASS1.LOG
encoded 1749 frames, 81.76 fps, 1850.89 kb/s
---------- RUN2PASS1.LOG
encoded 1749 frames, 81.89 fps, 1850.89 kb/s
---------- RUN3PASS1.LOG
encoded 1749 frames, 81.88 fps, 1850.89 kb/s
---------- RUN4PASS1.LOG
encoded 1749 frames, 81.82 fps, 1850.89 kb/s
---------- RUN5PASS1.LOG
encoded 1749 frames, 82.00 fps, 1850.89 kb/s
---------- RUN1PASS2.LOG
encoded 1749 frames, 19.44 fps, 1826.21 kb/s
---------- RUN2PASS2.LOG
encoded 1749 frames, 19.47 fps, 1826.37 kb/s
---------- RUN3PASS2.LOG
encoded 1749 frames, 19.44 fps, 1826.38 kb/s
---------- RUN4PASS2.LOG
encoded 1749 frames, 19.46 fps, 1826.38 kb/s
---------- RUN5PASS2.LOG
encoded 1749 frames, 19.44 fps, 1826.38 kb/s
I'm kind of proud of my super cheap little CPU! It's faster clock-for-clock than the X2 6000+ and probably consumes atleast 40W less.
4GB DDR2-833MHz 5-5-5-15
Asus P5B
Windows XP SP2
---------- RUN1PASS1.LOG
encoded 1749 frames, 81.76 fps, 1850.89 kb/s
---------- RUN2PASS1.LOG
encoded 1749 frames, 81.89 fps, 1850.89 kb/s
---------- RUN3PASS1.LOG
encoded 1749 frames, 81.88 fps, 1850.89 kb/s
---------- RUN4PASS1.LOG
encoded 1749 frames, 81.82 fps, 1850.89 kb/s
---------- RUN5PASS1.LOG
encoded 1749 frames, 82.00 fps, 1850.89 kb/s
---------- RUN1PASS2.LOG
encoded 1749 frames, 19.44 fps, 1826.21 kb/s
---------- RUN2PASS2.LOG
encoded 1749 frames, 19.47 fps, 1826.37 kb/s
---------- RUN3PASS2.LOG
encoded 1749 frames, 19.44 fps, 1826.38 kb/s
---------- RUN4PASS2.LOG
encoded 1749 frames, 19.46 fps, 1826.38 kb/s
---------- RUN5PASS2.LOG
encoded 1749 frames, 19.44 fps, 1826.38 kb/s
I'm kind of proud of my super cheap little CPU! It's faster clock-for-clock than the X2 6000+ and probably consumes atleast 40W less.
Re: I fell asleep
There are several manufacturers making mobos with nForce 6150 chipsets with integrated graphics, pretty much all of them mATX. Hmmm, looking around they seem to be shifted out a bit, probably in favour of the newer nvidia integrated graphics chipset. Newegg still has Foxconn, Asus, DFI and Abit versions of it, but I know that Gigabyte and MSI also had mobos based on it out.graysky wrote:Cool man, thanks for the results. Can you report your mem timings and final mem core rate (i.e. 5-5-5-15 @ 400 MHz) Also who makes your motherboard? I never heard of a 6150 chipset.
-
- Posts: 20
- Joined: Sat Aug 11, 2007 8:15 am
Re: I fell asleep
Sure.graysky wrote: Cool man, thanks for the results. Can you report your mem timings and final mem core rate (i.e. 5-5-5-15 @ 400 MHz) Also who makes your motherboard? I never heard of a 6150 chipset.
nVidia made the chipset. Similar to the 6100 and, from what I've read, the 7025 and 7050 chipsets.
It's Kingston Value RAM running at SPD DDR-400 PC3200. Nothing exotic. No heatspreaders or RAM fans. I looked in the BIOS, but there's nothing but "AUTO" in the settings. SPD.
It's a MSI K8NGM2-FID motherboard. I don't know if this long URL will work. http://global.msi.com.tw/index.php?func ... =&cat3_no=
Nothing fancy about it.
CPU-Z has the RAM timings. 3-3-3-8 @ 200MHz. CPU is 11 x 200 MHz. Code name Toledo.
thanks notquitequiet for that data, I've just ordered the 4200+ for my s939 board, we'll see how it compares to the 4400+.
looks I'll double my speed at least, for x264. hope it also impacts xvid encoding with agk like that.
perhaps ill do some overclocks first on the old 3000+ just to see how fast it can go
looks I'll double my speed at least, for x264. hope it also impacts xvid encoding with agk like that.
perhaps ill do some overclocks first on the old 3000+ just to see how fast it can go
Forgot to mention earlier: I'll be re-running the test at the exact same frequencies but using my E6600 instead (4MB L2 instead of 1MB).
Heheh... Thought so. Always nice to see some swedish on predominantly english boards, though.graysky wrote:Sorry dude, I have no idea how to speak the language. I just looked up Swedish on wikipedia and there was a list of common phrase
Impressive! You got it just right. *hands over giant cookie*jaganath wrote:I have minimal knowledge of swedish, but i think he said "Ah, are you swedish? and why did you write "I am fine, thanks!"? do I get a cookie?
As of 20-Sep-2007, we have data on over 100 Intel-based systems and on over 40 AMD-based systems. There are a few trends I picked-up on while browsing through the database. I put them into a single table and color coded them to make them easier to see. If you see a trend I missed, lemme know and I'll add it to the table.
Request: we don't have a single example of a machine that has both WinXP and WinVista on it. If you have a dual-boot setup, it would be cool to see the difference the O/S makes. Another missing trend is a 32-bit O/S vs. the same O/S that's 64-bit.
On to the table:
Yellow: Nearly 1:1 increase by adding an additional processor to a dual-chip MB
Orange: Some operating systems seem to handle x264 more efficiently than others
Red: Insignificant gain by upping the DRAM speed by 50 %
Blue: For the most part, these chips scale in a pretty linear fashion
Green: Tighter/looser memory timings have a pretty insignificant effect
Purple: Keeping the same over-all clock speed using a different combo of multiplier and FSB can give pretty insignificant gains
Again, I only gave this a once-over look; please point out any trends you see that I missed and also don't forgot about the O/S request!
Thanks again to all who contributed!
Request: we don't have a single example of a machine that has both WinXP and WinVista on it. If you have a dual-boot setup, it would be cool to see the difference the O/S makes. Another missing trend is a 32-bit O/S vs. the same O/S that's 64-bit.
On to the table:
Yellow: Nearly 1:1 increase by adding an additional processor to a dual-chip MB
Orange: Some operating systems seem to handle x264 more efficiently than others
Red: Insignificant gain by upping the DRAM speed by 50 %
Blue: For the most part, these chips scale in a pretty linear fashion
Green: Tighter/looser memory timings have a pretty insignificant effect
Purple: Keeping the same over-all clock speed using a different combo of multiplier and FSB can give pretty insignificant gains
Again, I only gave this a once-over look; please point out any trends you see that I missed and also don't forgot about the O/S request!
Thanks again to all who contributed!