But how did you determine that? I just looked at my servers and their specs only match server class Xeon processors (Skylake 16MB L3) so not sure how it is possible for them to be consumer.
I don't remember exactly. A couple of years ago you could determine that there was actually no xeon of that architecture that would fit with the GHz. Since they are obscuring the actual CPU in their linux kernel you can't read the model number outright. I going from memory here, but that was the gist of it.
Still using swap file? Memory is cheap. I don't recall a server where I created swap partition or swap file.
Memory is NOT cheap, not at all.
It is if you own it. If you rent your hardware, yeah, it adds up.
Even if I own it, throwing away 2-3GB of RAM makes no sense. Now, if I own it, I can easily assign 4GB of RAM then remove it once installed, by why? That's harder to script and still no benefit.
It's a bad habit to see resources as cheap and so waste them just because you can. Extra memory doesn't improve performance, it hurts it (just the tiniest bit). And it's not free, if you always apply twice as much RAM as you use (or four times, here), that gets costly one way or another. Either you wasted money overspeccing in the beginning, or you are stuck buying more now.
To add to this- I have an error that started appearing after updating their Fedora 29 and 30 instances. Further testing found that the error appears in different regions using their server type template installers or even a custom iso option that I used with net install. All I have to do is deploy, run dnf update and reboot. The error is present in every boot after the update. https://mangolassi.it/topic/19903/fedora-29-and-30-edac-skx-can-t-get-tolm-tohm-error-on-vultr
This isn't exactly related to OP's post...
It would be nice if there was a "clean & easy" way to "migrate" your vm's from Vultr to say a co-lo.
If you use a DevOps system, then there always is. If you use normal backups like Veeam, it's easy, too. Same with any platform, platforms don't make lock in, that comes from how it is set up. It's as easy to go from Vultr to colo as from anything else to colo.