
On a gigabit wired connection, I would see read/write speeds in the 30 MB/s range. The router hardware, including the processor and RAM (yes routers have processors and RAM), the USB controller in the router, and finally, the single hard drive. That configuration has terrible performance because of multiple bottlenecks. In the past, my NAS solution was nothing more than an external hard drive connected to my Wifi router. Transferring files over USB thumbsticks was becoming a pain. Octopus Deploy provided me with another laptop. I have a desktop for gaming, and photo editing, a laptop for travel, and my wife has a laptop as well. Regardless if I am working from home, my house needs a NAS to share files between computers.

In this article, I will walk through my thought process, along with the lessons I learned. In doing so, I have learned quite a bit about how hypervisors actually work. Did I really need two separate servers? I had a few weeks off of work, so I decided to work on combining the two into one MegaServer running Unraid. The funny thing was, I wasn't pushing either box all that hard. For almost a year, I had two servers sitting in my home office. So I built a new computer just to be a hypervisor. I needed more VMs than I thought my Unraid box could handle. This is where my misunderstanding of hypervisors came in.

At first, I used Unraid as both my NAS and a simple hypervisor. That misunderstanding caused me to end up building two servers. When I started, I had some fundamental misunderstandings on how hypervisors work. Specifically, how I built a NAS and a hypervisor to host a bunch of VMs for a test lab. What I want to focus on for this post is how I built the infrastructure to help me work from home more efficiently. I'll get into those differences in later posts. As expected, working from home is a lot different than working in an office. I've been working from home since April of 2018 for Octopus Deploy.
