4 ms·
Personally for me the $5 ones no longer work. Nightly "dnf update" gobbles up >1GB of memory for God knows why and kills off httpd or application server randoml
by habibur 4y ago
Personally for me the $5 ones no longer work. Nightly "dnf update" gobbles up >1GB of memory for God knows why and kills off httpd or application server randomly.
But a ~$10 virtual box with 2GB of RAM works fine. Nothing to complain. I get 2TB transfer and 50 GB space.
- trollied 4y agoI just add a 4Gb swapfile using a file on the filesystem, works just fine.
- ddtaylor 4y agoSame. I even have some scripts in the past that would use more memory for some operations that would first add extra swapfile, do stuff, then remove it after.
- sys42590 4y agoAgreed, a swap(file) on a NVME SSD can keep the kernel's OOM killer away while still yielding quite acceptable performance under many workloads.
- mongrelion 4y agoThank you for this. I have been having some issues recently with one of my servers and my solution was to increase the size of the tmp mount but that's basically a Russian roulette. Enabling swap during the update sounds like an elegant solution.
- MonkeyClub 4y ago> Nightly "dnf update" gobbles up >1GB of memory for God knows why It’s for packagekit, which is known to suck in this way. A `systemctl restart packagekit` right after the update will immediately drop it below 30MB.