Main > Main Forum
4Ghz Core 2 Duo vs M.A.M.E. 0.120 (benchmark results)
taz-nz:
--- Quote from: Tiger-Heli on November 06, 2007, 06:11:57 am ---
--- Quote from: taz-nz on November 06, 2007, 02:49:47 am ---If anyone know how I can extract from mame a complete list of parent ROMs based on the driver they used let me know.
--- End quote ---
Emuloader might be able to do this, depending on what you are looking for - also I think BuddaBing wrote a -listgen utility that would likely do a better job of that.
--- End quote ---
thanks I'll check it out, I look for a way I can create a benchmark call file for a large number of roms without a lot of typing, if I can please a plain txt list, i can soon right a bit of code to format it into a batch file.
--- Quote from: ozzi22 on November 06, 2007, 10:42:37 am ---I wonder what the bench marks would be on linux 64
--- End quote ---
I would to like to see 64 bit linux benchmarks results too, but I unlikely to be running them any time soon, Linux + latest chipset motherboard + raid array = come back in 6 months when we there are drivers. (atleast that been the story the last 3 times I tried to install Linux on a new machine)
--- Quote from: ahofle on November 06, 2007, 11:00:32 am ---This is slightly off topic, but also slightly on topic. ;D
Last night I overclocked my E6750 from 2.66 Ghz to 3.2 Ghz. I simply adjusted the FSB to 400 Mhz and set the memory to 800Mhz for 1:1. I was expecting to have to go back in and adjust the voltage, but I can't seem to make the voltage any lower than it already is (1.30 - 1.31V). It seems to be running fine, but most of the guides I've read have people trying to find the minimum stable voltage to minimize heat and I have no way of decreasing the value (only increasing). ??? This is on an Abit IP35 Pro mobo.
--- End quote ---
Your talking about undervolting and it's normally do to reduce heat and power useage, I have an undervolted and underclocked Athlon64 3000+ in my media box with passive cooling. People also undervolt with extreme cooling systems like phase change systems, but it your only useing air cooling you should be run stock voltage up to able 3.4-3.6ghz then you will need to increase it to overcome Vdrope, the catch is the more voltage you put in the more heat your cpu produces, the higher the CPU core temp the higher the voltage generally has to be to make the system stable, there is a point of zero return where all your doing is cooking your CPU.
--- Quote from: xmenxmen on November 06, 2007, 11:15:46 am ---Refurb HP a6152n, Core 2 Quad Q6600, 3GB, 400GB, Vista Premium, $550 + $12 shipped (Frys Online)
http://www.fatwallet.com/t/18/778709/
Enjoy!!!!
--- End quote ---
Good price on the surface, but it an HP box, so gutless 350watt PSU, no talk of the chipset used so probably something nasty, the bios will have zero overclocking settings. 3gb of points to another weild setup, probably only DDR2-667. If your looking for a cheap box with vista it's ok, but useless for overclocking or preformance computing. Stay away from brand name PC where ever possible they are built to look good and be cheap, and make the manufacture great margin at the same time, they hide a list of sins then you crack the case.
u_rebelscum:
--- Quote from: taz-nz on November 06, 2007, 02:49:47 am ---If anyone know how I can extract from mame a complete list of parent ROMs based on the driver they used let me know.
--- End quote ---
Hmm, mame -ls gives a full list, parents and clones. For not a complete list, there are maws (driver list), and the source files (of course ;), look at list at end of the file).
However, you'll have do some sorting to get the parents. One way, in the source, the GAME MACRO goes:
GAME( YEAR, NAME, PARENT, MACHINE, INPUT, INIT, ROT, COMPANY, FULLNAME, FLAGS )
If the parents part is 0 then it's a parent, otherwise it's the name of the parent.
Tiger-Heli:
--- Quote from: taz-nz on November 06, 2007, 02:55:28 pm ---thanks I'll check it out, I look for a way I can create a benchmark call file for a large number of roms without a lot of typing, if I can please a plain txt list, i can soon right a bit of code to format it into a batch file.
--- End quote ---
I know EL can select only parent ROMS (and roms based on game CPU or driver, for that matter) and can export the selected games to a text file. I don't recall, but I think the text file might have:
mame=aburner
mame=asteroid
mame=bzone
etc.
but a little bit of search and replace "mame=" with "" in Word or a text editor might get you what you want, I hope!
u_rebelscum:
--- Quote from: taz-nz on November 06, 2007, 02:49:47 am ---If anyone know how I can extract from mame a complete list of parent ROMs based on the driver they used let me know.
--- End quote ---
Oh, and -listxml, too, but as is it's, umm, bulky. RomLister can convert the xml to a list, as well as sort out clones, and output a batch file to run games.
taz-nz:
--- Quote from: u_rebelscum on November 06, 2007, 05:10:10 pm ---
--- Quote from: taz-nz on November 06, 2007, 02:49:47 am ---If anyone know how I can extract from mame a complete list of parent ROMs based on the driver they used let me know.
--- End quote ---
Oh, and -listxml, too, but as is it's, umm, bulky. RomLister can convert the xml to a list, as well as sort out clones, and output a batch file to run games.
--- End quote ---
Thanks for the tip worked great, created the XML file imported it into Romlister, filtered it for all working parent ROMs, and saved the list to a txt file. (3125 roms in total) Whipped up a bit of code in QBasic to turn the list of roms in to a call file for the benchmarking batch I use. (Yes I used Quick Basic, 8 lines of code and no need to compile.)I set the call file going and let it run for about 2.5 hours it got though about 350 roms, the worst score was for finalapr @ 5.99% you figure that one out.
I need to whip another bit of code to turn all the resulting txt files in to one file with all the ROM names and results. I may set the call file going and just let it run one day while I'm at work and see what I get in the way of result, some ROMs will get insane scores because they need user input to get pass the test screens, I seen a couple already that have scores around the 12000% mark. Probably not much use as a preformance test, but good for picking out the those roms that still have preformance issues.