Home › Forums › FABRIC General Questions and Discussion › What is the node storage class –NVME/SSD?
- This topic has 2 replies, 2 voices, and was last updated 3 years ago by
Xusheng Ai.
-
AuthorPosts
-
May 8, 2022 at 4:23 pm #1753
Hello,
I request a slice with a default disk space setting, 10GB. I checked the github but didn’t find out that the storage class. I was wondering if the node storage type was SSD or NVME? Also, How could we apply for a different storage class when we create a slice.
Thanks,
Best Regards,
Xusheng
-
This topic was modified 3 years ago by
Xusheng Ai.
May 9, 2022 at 9:18 am #1757The default storage in one of your VMs is a virtual block device attached to the VM and mapped to the VM’s host’s local disk. The host’s local physical disk is an SSD (i.e. not an NVMe drive). The performance of these virtual block devices is a bit difficult to assess because the virtualization is optimizing a lot of things for you.
Some things that will affect the performance of your local disk:
- The VM’s operating system will cache files in memory using any free memory allocated to your VM. Repeatedly accessing any file that is smaller than your VM’s free memory will likely be very fast because it will only read/write to memory. You can explicitly skip this cache. For example, if you use the
dd
command you can addoflag=direct
and it will skip this cache. - The host’s hypervisor uses any free physical memory to cache any virtual disk blocks used by the VMs that it is hosting. Repeatedly accessing the same block of a disk in a VM will likely be very fast because it will only use blocks that the host hypervisor is caching in its memory. This cache is shared by all VMs on that host and the availability of this cache depends on the way other VMs are using their disk blocks. There is no way for a user to choose to skip this cache.
- The physical disk is an SSD. Even if you manage to write to the physical disk, it should be faster than if you were using a spinning disk.
- Currently, most hosts on FABRIC have a couple hundred Gigs of memory and are underutilized. In most cases, accessing a local disk will only result in memory reads/writes. This may change as the testbed utilization increases.
If you want to use an NVMe drive you need to add an NVMe drive component to your VM (like how you add an NIC component). Checkout the NVMe examples listed the in the “start here” Jupyter example notebook.
Paul
May 11, 2022 at 9:16 am #1758Thank you so much! That definitely helps a lot.
-
This topic was modified 3 years ago by
-
AuthorPosts
- You must be logged in to reply to this topic.