2100 advertised as 4GBs… but isn’t.

Edit to clarify: I'm referring to RAM not storage space.

Silly question given the 2100 is supposed to have 4GBs, but how much does everyone else's have? I ask because mine has been slowing for some years and I've been suspecting wear of the eMMC being the cause. I thought of enabling ramdisks, but just with the dashboard open and my phone streaming YouTube, it hovers around 34-35% … of 3394MiB, according to the dash. 3394 MiB is not 4GiB (which is what most people expect when they read GB). Until now I didn't care enough to comment because it worked and was enough, but now that I want to use RAMdisks, it no longer is based on Netgate's own documentation. I run just pfBlockerNG and my lists of blocked things total about 900k based on the pfblockerNG dashboard widget (the sum of the numbers in the Count column), so I wanted to go with the recommended 512/1024 for /tmp and /var based on the documentation, but that would exceed my total remaining available RAM of 1.44GiBs. I could really use that extra half gig that was advertised right now.

Current usage in the Advanced->Miscellaneous page of /tmp and /var is 264 KiB and 22.48 MiB respectively. Based on the 900k count, and 1.44 of 3.3 GiB available, what should I set the values to?

Would values like 384/676 be workable and not cause problems during a system upgrade?

Edit 3: Welp I just tried 384/676 and had a brief panic as pfSense stopped responding (gave a DNSPROBE_FINISHED_NO_INTERNET error) _after I signed back in… but then it began responding again, making me sign back in again(??) after the reboot. I really don't want to brick it but it seems okay at the moment.

/tmp is fine but /var is now half full at 395/676M whereas it was at 22M pre-reboot… so… I don't know what to think.

Oddly, I had to trigger a manual update of pfBlockerNG lists because some of them disappeared after the reboot… I don't know why. I watched the Disk widget closely throughout the update and now my /var (with tmpfs RAMdisk) is hovering at 66% full which is unnerving, but everything seems okay now and nothing blew up. My 2100 is so slow now it took 14 minutes to fully run the update. 😬