RAM use of WHDLoad launchers

[Radertified]

I decided to look at RAM usage of different WHDLoad launchers. Results are as follows, in order from least RAM used to most RAM used:

• TinyLauncher (3,560 scanned): 512,800 bytes used (121,400 chip / 391,400 fast)
• LazyBench (3,563 scanned): 1,109,440 bytes used (448 chip / 1,108,992 fast)
• X-Bench (3,769 scanned): 1,123,672 bytes used (118,120 chip / 1,005,552 fast)
• AGS2 (3,563 scanned): 1,343,536 bytes used (870,208 chip / 473,328 fast)
• Multiview (3,563 scanned): 1,610,936 bytes used (936 chip / 1,610,000 fast)
• AmigaGuide (3,563 scanned): 1,757,544 bytes used (1,008 chip / 1,756,536 fast)
• iGame (3,563 scanned): 2,805,032 bytes used (1,296 chip / 2,803,736 fast)
• KGLoad (3,563 scanned): 3,446,288 bytes used (658,472 chip / 2,787,816 fast)

Notes:

• I used RetroPlay's WHDLoad games archives. There are 3,563 in my install. The number scanned by the launcher is shown next to its title.
• This is completely unbiased. I have no launcher preference.
• This isn't scientific. My methodology may be perfect, or it may be flawed. I personally think it's fine so if you disagree, oh well. The process was:
  • Restart WinUAE before testing each launcher to ensure nothing is resident in RAM and may interfere.
  • Get RAM use right before opening the launcher using the WinUAE debugger 'Tm' command.
  • Launch and go to the Games list in the launcher.
  • Get RAM use using the WinUAE debugger 'Tm' command.
  • Subtract to get overall RAM use.
• This isn't about which launcher scans/performs/etc. the best. This is strictly about RAM use from launch to games list display.
• All images and metadata were deleted from the launchers so the only thing that's used is the game title and path to the .info, or launch command.
• When no inbuilt scanner was available, I had to write my own database generator. Launchers that needed this are AGS2, KGLoad, LazyBench, AmigaGuide. No, I will not release these since they are craptacular.
• X-Bench decided to be weird and scan in 200 extra files. Maybe readme's?.

Hope someone finds this interesting.

[Retro-Nerd]

I know that TinyLauncher kills itself and clears the ram completely after the slave file is started. Would assume that the most WHDLoad launchers do it the same way.

[Radertified]

I didn't test that, but yeah, the ones that are written as WHDLoad launchers probably do. AmigaGuide/Multiview and LazyBench are generic so they likely stay resident.

[killergorilla]

Wahoo! I won!

Yeah KGLoad killed itself and reloaded afterwards