| Main > Main Forum |
| File with CPU requirements? |
| << < (2/2) |
| mahuti:
We actually had something like this on the Mac side that benchmarked the FPS on a selection of standard roms that we tried out, and the results varied from computer to computer on the exact same configuration. Could have been due to background processes, videocard, etc. Basically MAME replayed a game recording and once it was done we took down the average FPS, and a whole bunch of other information about the computers, with detailed instructions on the setup, etc. Didn't do much for us. Still lots of confusion about configuration & the best version to use with x_rom. |
| jelwell:
As long as everyone understands that the level of detail is meant to provide a SCALE and not a measurement I think we're good. I'll start working on a batch file to automate this process. Joseph Elwell. |
| paigeoliver:
--- Quote from: jelwell on March 10, 2005, 10:15:24 pm --- --- Quote from: paigeoliver on March 10, 2005, 10:08:27 pm ---It is a decent idea, but man it would take a long time to implement, maybe if someone could right a benchmarking app/test file that could automat speed tests then it would be workable. Basically the app would run "mameVERSION.exe game -nothrottle -ftr 10000" for each and every rom and then record results. --- End quote --- Thanks! That's an awesome idea to start with. And it's fully automatable - assuming mame doesn't leak. I need like 60fps minimum to play a game? Joseph Elwell. --- End quote --- A few games are 53 and a few are 30 or 45 but like 98 percent of the games are 59-61. Plus, if you can get it fully automated like that (might want to program the app to skip any ok screens, or press any button screens), the we can get a bunch of people to run the benchmarks on different systems. One thing, to avoid situations where the results are radically different due to configs, there should be a rule requiring all tests to be done on a fresh unmodified config. Whatever mame spits out when you run mame.exe -cc should be the config used. |
| jelwell:
--- Quote from: paigeoliver on March 11, 2005, 12:11:17 pm ---A few games are 53 and a few are 30 or 45 but like 98 percent of the games are 59-61. Plus, if you can get it fully automated like that (might want to program the app to skip any ok screens, or press any button screens), the we can get a bunch of people to run the benchmarks on different systems. One thing, to avoid situations where the results are radically different due to configs, there should be a rule requiring all tests to be done on a fresh unmodified config. Whatever mame spits out when you run mame.exe -cc should be the config used. --- End quote --- I'll add alan's tweaks to avoid all the ok screens (they're already added to my custom mame build). One step at a time with the config issues. Joseph Elwell. |
| krick:
--- Quote from: jelwell on March 11, 2005, 01:56:08 pm ---I'll add alan's tweaks to avoid all the ok screens (they're already added to my custom mame build). One step at a time with the config issues. --- End quote --- Are you using the standard MAME build environment? Just checking. Using different compilers and/or build settings can make a HUGE difference in framerate. |
| Navigation |
| Message Index |
| Previous page |