The truly "next gen" performance was Intel's Optane 3D XPoint, but that is ludicrously expensive.
And even then it's like boot from SSD 12 seconds at $130 dollars vs Optane 10 seconds at $1200.
The truly "next gen" performance was Intel's Optane 3D XPoint, but that is ludicrously expensive.
And even then it's like boot from SSD 12 seconds at $130 dollars vs Optane 10 seconds at $1200.
Now I do stuff like doing grep (well, ripgrep really) on an entire home dir, compute often hashes of files and things which may not be considered "regular use cases" but which I think are still "regular" or at least semi-regular when doing software development.
To me PCIe 3.0 x4 (or now 4.0 x4 I guess) NVMe M.2 vs SATA is day and night.
Here is loading times for windows and some blind tests:
Your personal experience could be down to several factors.
For example - wear of your devices, how much your SSD was occupied, drivers, other components being updated as well, etc.
Early SATA SSD has performance consistency problem, QD1 not as fast, etc.... they were way faster than HDD, but not perfect.
NVMe started off with controller that has already been fine tuned, hence comparing them to SATA SSD tends to be a lot faster. Now if you have similar controller on NVMe and SATA you might only notice the difference in the video. But the context still matters.
But assuming that NVMe and SATA SSD controllers emit the same energy, it makes more sense that NVMe would be hotter.
Think about it. If you throw a ball of high heat meat would it cool faster if it was connected to a large body of water (SSD with its chasis) or a small body of water (NVMe small piece of plastic that is the NVMe)?
Another thing to check if your NVMe either has proper thermal pads placement and/or if the air from the front coolers is reaching it.
Which is ironic because NVMe was supposed to be more efficient and doing less work because it's design wasn't bound with SATA&spinning assumptions and controller doesn't need to handle pcie-SATA conversions since it's directly connected to the bus etc.
One problem with m.2 is the spec would permit a module with the controller on the bottom where it would be difficult to cool. But I think so far nobody has been dumb enough to ship one.
There's also the location of the temperature probe, it doesn't need to be much further away from the heat source to register drastically lower temperatures in either case.
m.2 is a form factor, or really sort of a family of form factors.
SATA and NVMe are protocols and interfaces. In m.2, there are 12 key indexes. Drives use indexes B and M. m.2 support both NVMe and SATA. NVMe drives for m.2 are keyed at index M. M.2 SATA drives are keyed at B or often both B and M.
m.2 supports SATA and NVME, sometimes but not always in the same slot. For NVMe speeds, you need an NVMe drive. Those come in PCIe x2 and PCIe x4 at PCIe 3.x and PCIe 4.0 revisions of the standard. The drive and slot must both support this. m.2 SATA 3 drives don't have two cables to them like a 2.5" SATA 3 drive usually does. It goes in an m.2 slot that supports SATA and is keyed appropriatly.
m.2 also has various lengths: 40mm, 60mm, and 80mm. Some drives are up to 110mm and many boards provide for that. The "2260", "2280" and so on are drive sizes, 22m by the length.
m.2 also supports non-drive cards like GPS, Bluetooth, WLAN, WWAN, or NFC.
Another, earlier than m.2, standard allowed drives with a SATA interface on a card with no cables. That was known as mSATA.
As a developer I would just have to disagree.
After using NVMe SSDs for a while, using SATA SSDs suddenly feel like I’m on spinning rust plates.
To me it’s a night and day difference.
But yeah, you generally use Optane either as render cache or for non-volatile RAM. Or a ridiculously fast SSD drive.