MeGUI CPU Time Test - Compare different CPUs encoding the same file

[graysky]

I started a thread over at doom9 inviting people with MeGUI installed on their machines to download a small mpg clip with processing scripts and run it, then report the results for the purpose of comparing different CPUs processing the same file. I'd like to extent that same invitation to the folks here and I will compile the results and update both threads.

The test files are in rar format and contains a small (43 meg) mpeg-2 clip with the an avs script file, d2v file, the jobs etc.

To participate, you'll need to have MeGUI (which needs dotnet 2.0) and Avisynth installed. Here are links to d/l them:

dotnet 2.0
MeGUI
Avisynth

Download to test files has been removed since >2 weeks of inactivity.

UPDATE:The results to-date were using a pretty aggressive avs file. I have since updated the files and made a new test.rar -- if you participated in the test PLEASE DELETE YOUR C:\WORK AND WORK.RAR and download the new one from the same URL which uses a more realistic avs file. The new test doesn't require you to mess with the threads setting at all - it is automatic for everyone. I'll start populating a new table with your new results. I started with my own.

Thanks all!


Update: 25-Mar-07
Have a look at the post by aicjofs here where he shows that using mt.dll on the work.avs I provided can translate into an addition boost of ~14 % on his QX6700.

-------------------------------------



If you keep your CPU:Mem bus 1:1, you'll find that the data scale in a highly linear fashion albeit short of the theoretical maximum. Here is a little analysis on chantmak's data to this end.



Finally, here is a subset of the data showing that, at least with MeGUI doing this avs, there is really no advantage to running with a higher FSB @ the same clockrate. Mem timing does seem to have an effect (last row). Have a look for yourself:

[Baldrick]

Also Athlon 64 X2 3800+ but 16.92fps,3.81fps(1 thread) and 22.47fps, 5.91fps (2 threads)

I guess that you wont get that many results here...we prefer one click tools and this was way too many steps....

[graysky]

Thanks for the data point, Baldrick. Too bad more people in here don't use MeGUI. I would really like to see an E6700 and X6800 datapoint.

[j4gg3rr]

Looks like the Athlon 64 X2 3800+ should be renamed to Athlon 64 X1.5 3800+

[Soopafresh]

graysky - Check out the thread on "Which CPU to Use for Avisynth" over at Doom9. The E6600 was twice as fast as the closest AMD competitor.

[graysky]

thanks for the link

[graysky]

Ha, finally upped the FSB on my machine from 200 to 225 and did the benchmark. The machine is actually stable at this level. Anyway, added to the table.

[graysky]

Got some optron data

[graysky]

Update to the table: we now have a quad core example -- thanks drjay!

[graysky]

UPDATE:The results to-date were using a pretty aggressive avs file. I have since updated the files and made a new test.rar -- if you participated in the test PLEASE DELETE YOUR C:\WORK AND WORK.RAR and download the new one from the same URL which uses a more realistic avs file. The new test doesn't require you to mess with the threads setting at all - it is automatic for everyone. I'll start populating a new table with your new results. I started with my own.

The URL is in the first post in this thread.

[graysky]

Ok! Updated the chart. Interesting that for O/C'ed machines, in general, the work values (1st pass FPS) seem to track closer to the clockrate than the total video encode time does... I still can't figure that one out.

[redwudz]

OK, the updated version:

[graysky]

OK, the updated version:

Cool man, just one question, do you know what core your 3800+ is? You can find out by running cpu-z and post the screenshot so I can get both the codename for the code, the multiplier, and the FSB (all in the same screeenshot). It'll look like this:



Thanks!

[redwudz]

Sure:

[graysky]

Thanks man... I'll update the table accordingly.

[graysky]

Updated the first post of this thread giving some info about mt.dll which can further boost your speed numbers with multicore processors.