Today we are taking a look at the Lexar NM620 1TB SSD. According to Lexar, the NM620 is a PCIe 3.0 NVMe SSD targeting “next-level performance for intensive workloads” and is built using an in-house Lexar controller. I do not normally quote vendors, but in this case I am setting up a context for what is to come in this review as we put Lexar’s claims to the test.
Lexar NM620 1TB NVMe SSD
The Lexar NM620 1TB comes in a single-sided M.2 2280 (80mm) form factor.
As mentioned, the Lexar is based on their custom controller which is labeled DM620. Not much is known about this controller, except that it can handle 3D TLC NAND and is DRAMless. The NAND on this drive is Micron 96L TLC (B27B), the same variety of NAND as used on a number of 2018-era PCIe 3.0 NVMe SSDs.
Since this is a single-sided drive, the back has nothing. It is actually so barren that my Canon EOS Rp autofocus had difficulty finding anything to focus on.
Lexar NM620 Specs
The Lexar NM620 line of SSDs is available from 256GB to 1TB.
The 1TB drive we are looking at is at the top of the product stack, with sequential read performance rated at 3300 MB/s, and sequential write performance rated at 3000 MB/s. By PCIe 3.0 standards these are fairly high-end numbers, so Lexar has some performance claims to live up to. Endurance is a bit low at 500TBW for our 1TB drive. In contrast, the Samsung 980 1TB and WD Blue SN550 1TB are both rated at 600TBW.
CrystalDiskInfo can give us some basic information about the SSD, and confirms we are operating at PCIe 3.0 x4 speeds using NVMe 1.4.
Test System Configuration
We are using the following configuration for this test:
- Motherboard: ASUS PRIME X570-P
- CPU: AMD Ryzen 9 5900X (12C/24T)
- RAM: 2x 16GB DDR4-3200 UDIMMs
- OS: Windows 10 Pro
Our testing uses the Lexar NM620 1TB as the boot drive for the system, installed in the M.2_1 slot on the motherboard. The drive is filled to 85% capacity with data and then some is deleted, leaving around 60% used space on the volume.
The important part of this is that we are using the same test setup for our M.2 drives so we can see what happens across the population with a consistent test setup. We also install the drives package to the motherboard (with a photo stop in-between) and do not perform any special configuration to simulate the real-world user experience. Again, same system, using automatic Windows configuration on all of these drives because we want as close to the real-world results as possible.
Next, we are going to get into our performance testing.