Main > Main Forum

4Ghz Core 2 Duo vs M.A.M.E. 0.120 (benchmark results)

Pages: << < (19/104) > >>

taz-nz:

CPUROMDriver      0.119         0.120         0120u1       0120u2     0.120(64)    0.120u2(64)    0.120u3(64) E6400 @ 3.4ghz    crusnusa   midvunit.c212.24%212.12%178.27%182.84%  n/a220.81%     n/aE6850 @ 4.0ghzcrusnusa   midvuint.c257.69%257.32%218.20%214.79%271.81%269.31%   277.86%   E6400 @ 3.4ghz    starblad   namcos21.c234.33%120.83%116.97%119.37%  n/a127.74%     n/aE6850 @ 4.0ghzstarblad   namcos21.c299.30%144.10%144.00%142.10%153.57%150.71%   150.75%   E6400 @ 3.4ghz    gauntleg   vegas.c47.92%114.97%132.38%139.10%  n/a163.50%     n/aE6850 @ 4.0ghzgauntleg   vegas.c68.91%166.17%173.07%166.03%183.42%191.32%   200.33%   E6400 @ 3.4ghz    blitz   seattle.c122.25%87.86%111.59%113.12%  n/a145.63%     n/aE6850 @ 4.0ghzblitz   seattle.c153.43%138.59%143.28%136.99%164.15%185.35%   172.56%   E6400 @ 3.4ghz    daytona   model2.c   n/a86.18%87.22%89.09%  n/a120.89%     n/aE6850 @ 4.0ghzdaytona   model2.c   n/a106.17%106.43%104.94%142.72%140.42%   141.41%   E6400 @ 3.4ghz    gradius4   hornet.c60.36%79.34%   n/a97.97%  n/a79.57%     n/aE6850 @ 4.0ghzgradius4   hornet.c116.72%164.94%   n/a180.32%122.16%125.69%   128.15%   E6400 @ 3.4ghz    radikalb   gaelco3d.c77.46%76.11%95.72%109.88%  n/a163.93%     n/aE6850 @ 4.0ghzradikalb   gaelco3d.c94.25%93.97%116.77%129.44%150.07%200.22%   196.07%   E6400 @ 3.4ghz    ridgerac   namcos22.c65.56%64.73%90.77%92.37%  n/a147.79%     n/aE6850 @ 4.0ghzridgerac   namcos22.c80.00%79.54%114.89%112.44%106.77%194.55%   177.79%   E6400 @ 3.4ghz    scud   model3.c34.41%32.91%33.00%33.88%  n/a28.48%     n/aE6850 @ 4.0ghzscud   model3.c41.21%39.60%39.56%38.93%33.81%33.89%   30.36%   
No big preformance changes with 0.120u3, the biggest change in my mind is that SCUD no longer looks like a strobe light, but still has a lot of graphics issues.


--- Quote from: TheManuel on November 09, 2007, 09:12:11 pm ---
I am a little frustrated.
I have tested i686, PM and P3 builds of MAME and they all yield virtually the same result, at least on the game I am benchmarking against which is Mace (it sucks, by the way).
Could I be missing something?  Even the -mt parameter makes no difference and I did set osdprocessors=2.

I am using the same command line parameters as tar-nz on my Core 2 Duo e4300 overclocked to 2.4GHz.  I would like to see the same kind of improvements (proportional to my processor speed) tar-nz saw with the PM build but it is not working for me.

Any pointers will be appreciated.

--- End quote ---

I'm not sure why your seeing no difference with the -mt, there may be something else in your system that is limiting your prefomance, CPU FSB/Cache, memory speed or amount, graphics card. I did a little testing on the PM optimisation and it seams it lost some of it's edge with the new builds, probably due to the fact the drivers are now so much better optimised than the were before.

I compile two 32bit builds of mame 0.120u3 with and with out the PM swtich inable in the make file it then bench marked a selection of ROMs with both version with and without the -MT swtch.

ROM            STANDARD          STD -MT                  PM                   PM -MT

carneveil    220.38%            229.76%            222.15%            229.87%
a51site4     178.56%            186.05%            181.06%            187.67%
starblad      130.53%            136.82%            135.86%            142.34%
mace           193.00%            195.97%            189.39%            189.75% (32bit graphics bug)
gradius4     115.47%            120.49%            111.49%            115.96% (32bit graphics bug)
propcycl        68.68%              79.93%             71.29%             73.39%
crusnusa     223.62%            242.82%            226.68%            235.00%
gauntdl       110.27%            113.19%            108.82%            111.18% (32bit graphics bug)

As you can see some roms gain a few % with the PM optimisation, all the drivers with the u3 Build 32bit graphics bug drop a little.
It looks like the PM optimised build may have become obsolete with the last few release of MAME, the early build gain alot more for the optimised builds.


--- Quote from: divemaster127 on November 10, 2007, 12:23:03 pm ---Hey guys could I get a couple of opinions I have stopped setting up my new quad until i get some good feedback used to video did not matter but now which video card would you guys use
1. pci-e arcadevga or I have a extra 8800 gts laying around.
My monitor is a betson I did some performance test & the 8800 just runs all over the arcadevga.
thanks for your help
dm

--- End quote ---

If your Betson will run ok off the 8800 gts and you don't have another use for it already I probably use that, It total over-kill for MAME I only run a 8800 gts as I also PC game alot on my system. The 8800gt may have a preformance advantage with Vista, I wouldn't think you would see much difference in MAME benchmarks between the two cans in Windows XP, but as Vista likes to render the Aero desktop in the backgrond even when it's not visible,  the 8800gts may have an advantage there.



manny2003:

i remember reading that the guy who wrote the software SLI driver for rendering (he called in SLI because it splits the rendering between 2 or more cpus) said on his site that .120 builds through to u2 if you have a quad using OSDPROCESSOR=2 would be faster on a quad than using OSDPROCESSORS=4 because of the way the render code worked.

The work in progress for the 120u3 build of mame states as a feature that the renderer supports quad processors. (maybe that means there isn't a penalty for using OSDPROCESSORS=4,  or it could mean that it works properly.) He has also only added support for this SLI rendering for some of the drivers at this point (hence the resaon why some of them do no really get an improvement from the switch.)

-Manny

TheManuel:

Thank you for all the information and advice, taz-nz.  It sounds like recent versions of mame are already pretty well optimized so perhaps I should not concern myself to much with that.

One final question to all, though:
Is there a way to set the environment variable osdprocessor permanently in the registry or do we always have to set it before running mame to get the benefit?

Thanks.

tommy:

I didn't read this whole thread. Did anyone find Gauntlet Legends to be anymore playable with a good dual processor PC?

Tiger-Heli:


--- Quote from: TheManuel on November 12, 2007, 11:22:07 am ---Is there a way to set the environment variable osdprocessor permanently in the registry or do we always have to set it before running mame to get the benefit?

--- End quote ---
I would expect there to be a mame.ini file line for it, but haven't checked.

Pages: << < (19/104) > >>

Go to full version