Considering how often I see NVMe-related titles over the Internet, I consider NVMe-oF to be still a hot topic. That’s why I decided to pitch in 🙂
Today, I’ll talk about a thing that any sysadmin running Hyper-V VMs does (or still dreams about) while managing infrastructure resources: hot modifying assigned to VM memory amount. I’ll discuss not only the feature itself but also how it works on different OS and its impact on the environment stability.
All of us keep an eye on resource consumption within our environments. If a VM needs extra RAM to have the job done, we provide it with some, right? And, we usually run many VMs on our servers each with own purpose and configuration. That’s, actually, why changing the amount of assigned to a VM memory without rebooting it may come in handy. Also, many guys run some parts of their environments on Windows while having other parts run on something from Linux family. Looks pretty hectic in terms of management, doesn’t it?
Performance or protection? How Microsoft patches against Meltdown and Spectre influence CPU, RAM and Disks performance
In today’s topic, I’d like to talk about the Meltdown and Spectre vulnerabilities. But not about the harm they cause, this has been covered widely in numerous articles, but how Microsoft patches intended to protect you from the vulnerabilities, affect (if they do) the hardware performance. Before we take a deep dive into the tests and numbers, let me tell a few words about Meltdown and Spectre and outline the testing scope to make sure we speak one language.
Subscribe to our posts
- How is NVMe-oF doing? Part 1: Linux NVMe-oF Initiator + Linux SPDK NVMe-oF Target
- Setting up a Windows Failover Cluster for a home lab
- Performance comparison: SQL Server Failover Cluster Instance on S2D vs. SQL Server Basic Availability Groups on Storage Spaces. The battle starts
- Can SQL Server Failover Cluster Instances run on S2D twice as fast as SQL Server Basic Availability Groups on Storage Spaces? Part 2: Studying FCI performance
- Can SQL Server Failover Cluster Instance run on S2D twice as fast as SQL Server Basic Availability Groups on Storage Spaces? Part 1: Studying BAG performance