Another thing that I realized last night about the RAM—you're actually going to have even
less than 4GB because it's going to be dynamically shared with the integrated graphics. Now it's not my impression that Dolphin actually needs that much in the way of video memory, especially if you're running at the lower resolutions that would probably be required for decent performance, but it's still not great. For this reason, you might actually want to see if you have any options in the BIOS that let you configure memory exclusively allocated to the graphics which you'd actually want to set to the lower value possible (keeping in mind that some newer native PC games may refuse to launch if the value is set too low).
Worse still is that, because your main storage is only just an SD card, when you run out of RAM, things aren't going to perform all that well.
By the way, if you ever humor yourself and want to try the Linux route and see how its RAM usage works out, I remembered that you can actually install the OS itself onto a USB drive, and I don't mean the OS installer and/or ISO! So if combined with even just a SATA SSD running from USB 3.0, that could have substantially improved storage performance (and even USB 2.0 might not be too bad, though you'd be leaving a lot of disk performance on the table); at least in Linux Mint, the easiest way to install the OS itself to a USB disk is to simply remove all other internal disks—it'll just automatically pick the USB drive then (not counting the USB drive that the ISO itself is running from which I always just recommend doing via
Ventoy).
Also, I realized that, with only 4GB of shared RAM, it's questionable whether you'd even be able to install the Dolphin flatpak within a live ISO session anyway, thereby maybe requiring you to just straight-up install the OS proper, or maybe you could alternatively get away with just using of the
unofficial AppImage (click on "Releases" on the right side; once downloaded, right-click on the file ▶ Properties ▶ "Permissions" tab ▶ check "Allow executing file as a program", thereby allowing you to run the program by just double-clicking the file).
Other thing is that Linux has a neat function called "zram" that will actually try to first compress RAM when you start to run out, and then if you start to run out
again even when compressed is when it'll actually start to overflow by writing to the disk; even on a laptop with a
way weaker CPU (E-350) and integrated graphics paired with only 3GB of RAM when trying to run a program that wanted 4GB of RAM, launching said program easily took something like a quarter of the time simply by having zram installed. Some Linux distros actually have begun enabling it by default but, at least on Linux Mint, this can be enabled by simply launching the "Synaptic Package Manager" program, searching for "zram-config", double-clicking on it so that it becomes selected for installation, and then clicking the "install" button...and maybe restarting your PC once the install is done? (afterwards you can check zram usage by running
cat /proc/swaps in the terminal).
The
one niggle about zram is that it's basically trading CPU cycles for more RAM, and because that CPU only has two CPU cores which is what Dolphin primarily relies on, there's a chance that using zram could actually make performance
worse, but only if running Dolphin is able to actually fit within your system RAM when zram is
not installed.