On 12/5/24 09:59, Michael Stone wrote: > On Thu, Dec 05, 2024 at 09:42:08AM -0500, e...@gmx.us wrote: >> Is it different when you boot from an nvme drive? I have what I was >> told was one and it appears as /dev/sdb or /dev/sda depending how the >> OS feels that day. I didn't buy it new, it was given to me, so I may >> have been misinformed. It's a thing that looks like a SIMM, and when >> it's plugged in the motherboard disables one of the SATA ports, which >> is unfortunate. > > That is a SATA SSD, not an NVMe.
Interesting, thanks. Apparently either it was misrepresented to me, or I misremembered. That explains some stuff. > The SATA drive letters can change based on things like which drive starts > up faster or what removeable devices are plugged in, which is why using > UUIDs or somesuch is preferred over using the device name. And that probably explains why it's always sdb under a rescue thumb drive, because that environment doesn't automount _anything_. > SATA maxes out at 600MB/s, while PCIe is currently at 4000MB/s per lane, > with NVMe drives typically using as many as 4 lanes [16000MB/s]. How do I tell how many lanes a given drive uses (preferably before purchase)? > For many [most?] consumer applications the differences will not be > noticable.) Yeah, I probably wouldn't be able to tell. It's just geek points. I was thinking it might matter when xferring gigabyte+ files to the media server, but then the bottleneck would either be the CPU encrypting the SSH data, or the network itself. Is one kind more long-lived than the other?
