| Main > Main Forum |
| 4Ghz Core 2 Duo vs M.A.M.E. 0.120 (benchmark results) |
| << < (9/104) > >> |
| headkaze:
This post might help http://www.mameworld.info/ubbthreads/showthreaded.php?Cat=&Number=129879&page=0&view=expanded&sb=5&o=&fpart=1&vc=1 |
| John IV [MameUI64]:
Thanks for the run. Yes you're missing the fastest configuration of .120u1 at 64bit. The jumps Aaron made in the software sli and applying that to the other 3d drivers really gave some nice boosts. He does his 64bit builds [PTR64=1 ]w/out PM=1 so it will be interesting to see if there are any changes w/ PM=1. |
| taz-nz:
Since this thread is starting reads like a long list numbers, and the point of these benchmarks is to help out those of you looking to find out what you need to run the most demanding M.A.M.E. ROMs, I decided to post something other than benchmarks today, mainly because I'm still trying to wrap my head around two different Microsoft SDKs, 64 Mame compiling and my Hard Drives looks like MAMEDEV exploded all over them. So for all those of you wanting to build a preformance M.A.M.E. PC on a budget, I did a quick shopping list and then found some prices over at www.clubit.com (There may be better and cheaper places out there, but they had the right gear at what looked like the right price) GIGABYTE GA-P35-DS3R Rev. 2.0 LGA 775 Intel P35 ATX Intel Motherboard Retail $128.50 Cooler Master RR-CCH-LB12-GP Hyper 212 CPU Cooler $33.99 Intel Core 2 Duo E4500 M0 Stepping Conroe 2.2GHz 2MB L2 LGA 775 Processor Retail BX80557E4500 SLA95 $123.50 CORSAIR XMS2 2GB (2 x 1GB) DDR2-800 CL 5-5-5-12 Dual Channel Kit Retail TWIN2X2048-6400$74.50Sub Total: $360.49 Add a dirt cheap PCI-E VGA card, case with atleast a 400-450watt PSU & a 120gb HDD for your OS & MAME,and with a little overclocking you should hit 3.2ghz (8x 400fsb) and with a some more extreme overclocking and some luck you could get as high as 3.6ghz >:D (9x 400fsb), without the need for a lot expensive hardware. (I suggest dropping the Multiplier below 11x and increasing the FSB to 400mhz, as the P35 chipset will easily handle 400fsb and the extra bandwidth doing this will give you will help hide the any drop in preformance you may get from the E4500 having only 2mb cache.) That should get you 80-90% of my benchmark scores which as long as your running MAME64 0.120u1 in Vista 64, that will put most of the working ROMs on my benchmark list in the playable basket for you. --- Quote from: john iv on November 01, 2007, 01:23:38 pm ---Thanks for the run. Yes you're missing the fastest configuration of .120u1 at 64bit. The jumps Aaron made in the software sli and applying that to the other 3d drivers really gave some nice boosts. He does his 64bit builds [PTR64=1 ]w/out PM=1 so it will be interesting to see if there are any changes w/ PM=1. --- End quote --- As soon as I can get myself sorted with the whole compiling a 64bit build of mame, I'll post both In-game & CPU benchmarks for MAME64 0.120u1 with and without PM optimisation. (It really shouldN'T be this hard :P, but like I said I'm rusty, and the documantion on compiling MAME64 sucks.) --- Quote from: headkaze on November 01, 2007, 07:55:03 am ---This post might help http://www.mameworld.info/ubbthreads/showthreaded.php?Cat=&Number=129879&page=0&view=expanded&sb=5&o=&fpart=1&vc=1 --- End quote --- Thanks for the link, I think I have all the required files now, I've just got to install everything get everything in the right place on my HDD, and then I can try it all out. |
| John IV [MameUI64]:
Just FYI, I released the 64bit version of Mame32 .120.2 after going to Vista-64 the other night. Got some nice increases as you're seeing too. Game Driver Arguments .120.2-32 .120.2-64 Δ crusnusa midvunit.c -str 90 -video none -nosound -nothrottle -norc -nosleep 182.84% 220.81% 20.77% starblad namcos21.c -str 90 -video none -nosound -nothrottle -norc -nosleep 119.37% 127.74% 7.01% gauntleg vegas.c -str 90 -video none -nosound -nothrottle -norc -nosleep 139.10% 163.50% 17.54% blitz seattle.c -str 90 -video none -nosound -nothrottle -norc -nosleep 113.12% 145.63% 28.74% daytona model2.c -str 90 -video none -nosound -nothrottle -norc -nosleep 89.09% 120.89% 35.69% gradius4 hornet.c -str 90 -video none -nosound -nothrottle -norc -nosleep 97.97% 79.57% -18.78% radikalb gaelco3d.c -str 90 -video none -nosound -nothrottle -norc -nosleep 109.88% 163.93% 49.19% ridgerac namcos22.c -str 90 -video none -nosound -nothrottle -norc -nosleep 92.37% 147.79% 60.00% scud model3.c -str 90 -video none -nosound -nothrottle -norc -nosleep 33.88% 28.48% -15.94% Vista Ultimate 64 • Intel C2D E6400 3.5Ghz • 2GB Corsair DDR2 800 • ATI X1950 Pro 20.47% |
| taz-nz:
--- Quote from: john iv on November 03, 2007, 04:18:16 am ---Just FYI, I released the 64bit version of Mame32 .120.2 after going to Vista-64 the other night. Got some nice increases as you're seeing too. --- End quote --- Sweet, that saves me from another day of going around in circles trying to compile a 64bit build, Does this mean there will be an official 64bit of MAME32 from now on ? :notworthy: (I'd love a step by step how-to of what I need and where to put it, to make my own 64bit MAME builds if you have time to write one) Running MAME in 64bit really does make for some great improvements, but it's interesting that gradius4 CPU score takes such a hit in preformance when you jump to 64bit, where as the 32bit versions show an increase in preformance with each new build, yet the 64bit builds take a pounding. (Maybe it's a little too optimised for the 32bit Enviroment to work well in 64bit currently.) I ran a set of the pure CPU benchmarks on your MAME32 64bit build, and update the score chart. (I finally figured out why I wasn't getting an output to file from Mame32) CPUROMDriver 0.119 0.120 0120u1 0120u2 0.120(64) 0.120u2(64) E6400 @ 3.4ghz crusnusa midvunit.c212.24%212.12%178.27%182.84% n/a220.81% E6850 @ 4.0ghzcrusnusa midvuint.c257.69%257.32%218.20%214.79%271.81%269.31% E6400 @ 3.4ghz starblad namcos21.c234.33%120.83%116.97%119.37% n/a127.74% E6850 @ 4.0ghzstarblad namcos21.c299.30%144.10%144.00%142.10%153.57%150.71% E6400 @ 3.4ghz gauntleg vegas.c47.92%114.97%132.38%139.10% n/a163.50% E6850 @ 4.0ghzgauntleg vegas.c68.91%166.17%173.07%166.03%183.42%191.32% E6400 @ 3.4ghz blitz seattle.c122.25%87.86%111.59%113.12% n/a145.63% E6850 @ 4.0ghzblitz seattle.c153.43%138.59%143.28%136.99%164.15%185.35% E6400 @ 3.4ghz daytona model2.c n/a86.18%87.22%89.09% n/a120.89% E6850 @ 4.0ghzdaytona model2.c n/a106.17%106.43%104.94%142.72%140.42% E6400 @ 3.4ghz gradius4 hornet.c60.36%79.34% n/a97.97% n/a79.57% E6850 @ 4.0ghzgradius4 hornet.c116.72%164.94% n/a180.32%122.16%125.69% E6400 @ 3.4ghz radikalb gaelco3d.c77.46%76.11%95.72%109.88% n/a163.93% E6850 @ 4.0ghzradikalb gaelco3d.c94.25%93.97%116.77%129.44%150.07%200.22% E6400 @ 3.4ghz ridgerac namcos22.c65.56%64.73%90.77%92.37% n/a147.79% E6850 @ 4.0ghzridgerac namcos22.c80.00%79.54%114.89%112.44%106.77%194.55% E6400 @ 3.4ghz scud model3.c34.41%32.91%33.00%33.88% n/a28.48% E6850 @ 4.0ghzscud model3.c41.21%39.60%39.56%38.93%33.81%33.89% Looks like scud is the only ROM still holding out, but since it's a non-working rom and the emulation needs a lot of work, it only makes sense that it's scores are low. I had Task Manager open on the Preformance tab while running this lastest set of benchmarks, it showed that the model2.c & model3.c drivers are noticably lacking any form of multi-threading with one core being loaded to near 100% while the other is lucky to hit 10%, It will be interesting see if any of Aaron's software SLI magic can be applied to these drivers in the future. For those still interested I'll run a full set of In-Game benchmarks tommorow with the 64bit build of MAME 0.120u2, but in the mean time here's a preview: Propcycl: 0.120u2 (64bit) 151.88% 91.28fps Blitz: 0.120u2 (64bit) 171.18% 102.71fps Gauntleg: 0.120u2 (64bit) 142.84% 81.42fps |
| Navigation |
| Message Index |
| Next page |
| Previous page |