MeGUI CPU Time Test - Compare different CPUs encoding the sa
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:
