ACTIVE PROJECT: Work-In-Progress
I tried playing Star Citizen again to find that it would not run smoothly because my SSD was being held hostage as it was showing 100% usage the whole time.
My boot drive is a Samsung EVO 970 Plus M.2 NVMe. However, I do not have enough space to install and run Star Citizen on it, so why not experiment, I thought. My idea is to create a RAM disk on one of my Homelab servers and access the storage using Fiber Channel (FC).
My now 5-year-old computer architecture most likely causes these issues, but it gave me an idea I wanted to try out of curiosity.
I fired up my newest edition to the laboratory, a 1U SuperMicro with 2x Intel® Xeon® Processor E5-2660 v2, 128GB of DDR3 1333MHz ECC RAM, and 4x 2TB 10K SAS Drives.
After receiving the new (used) server hardware, I spent some time upgrading firmware and patching CVE’s related to this CPU model, so I already have the hardware prepared for a production environment. We will be using Proxmox Virtual Environment (Proxmox VE) for this experiment as we will be using virtual machines.
I created a VM with NUMA enabled for 20 CPU cores, 112GB of RAM, and 800GB storage, with a fresh install of Ubuntu 20.04 LTS.
I have no previous experience with using or configuring RAM disk on Linux. My first goal was to do just that and ensure data would persist on reboots. The first part of creating the RAM Disk happened to be easy enough as I already had experience creating and managing storage drives, so it didn’t take me more than 5 minutes to figure this one out. However, I still needed to make data stored on the RAM Disk persistent. For that, I managed to come across this blog post, Persistent Ramdisk on Debian/Ubuntu.
I am currently awaiting the delivery of parts to continue this experiment.