![]() Next I reclaim the devices so that the new SATP rules are applied. With the second command I mark the third disk as local. With the first command I mark the “second disk” as SSD and local. So this is what I did to get exactly that. In my testing I need local disks and need SSD. When I boot all disks are recognized as regular disks and in some cases as non-local. Third Disk – Large disk – 1TB – SCSI 2:0.Second Disk – Fake SSD – 40GB – SCSI 1:0.First Disk – ESXi install disk – 5GB – SCSI 0:0.Just to point out, I use 0:0 / 1:0 / 2:0 so that each device gets a new controller and is easy to identifiy: To keep things simple I set things up as follows. Those hosts have multiple disks and I want to mark one of those disks as SSD. In my lab I have a bunch of virtualized ESXi hosts. So what is my goal: Faking an SSD in my virtualized vSphere lab. For me I’m still pleased with the drive, as it has served me well for syncing & running my LAB VM-s between my different computers.I have written about this before (and so has William Lam, so all credits go to William), but I wanted to note down these commands for my own use as I find myself digging around often for the same commands these days. It doesn’t necessarily make the T7 a bad drive, but it’s just something to take into account. I used different files with sizes ranging from 1GB (like crystal disk mark) and up to 20GB. And not so large that they should overwhelm a M2 drives cache functionality/slow it down. And I was copying large files from internal M2 drives capable of more than that. Namely Samsung promises “up to 1000MB/s” writes and having tried it on multiple computers actually copying files onto it lands somewhere around 350MB/s for me. That although synthetic benchmarks like CrystalDiskMark show performance “like its written on the box” then real life differs from it. One more thing that I feel must be said about the portable M2 drive is. Yet it is something that would make VMs run sluggish. The results show in my case that the internal M2 drive is about 10% faster. Although it doesn’t change much the system itself is a Ryzen 5800x on a X570 chipset motherboard. The internal M2 NVME I use in the test is the Western Digital 1TB WD Blue SN550. That little idea I got from a nixCraft article. ![]() In order to measure latency/IO performance I used DD with a small block size. When comparing latency on a machine running on my internally installed m2 NVME drive and the USB-C connected Samsung drive there is no difference that I can feel when doing labs.īut as feeling isn’t actually accurate I thought I’d actually measure the IO performance. ![]() ![]() How it actually is with the Samsung T7 portable driveĪfter having done some research I opted to buy the 1TB Samsung T7 Portable SSD and long story short my use case works fine. And as reviewers somehow didn’t want to cover the latency aspects I was left wondering. I was wondering about the latency penalties that would come from having the NVME drive over USB instead the m2 slot. Previously only having owned USB3 HDD’s for back up purposes and having seen their latency issues/slowness I was quite skeptical. Syncing the Kali VM constantly between my workstation and my laptop was time consuming and well I mostly just forgot to do it. When I started more actively playing around on different hacking CTF platforms I felt the need to carry my “CTF pwn box” with me. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |