I should add that this only happens with steam

Did you mean Mbps (megabits) or MB/s (megabytes). Cz 350 Mbps (~43 MB/s) is very slow for an NVMe

Going off of steams UI its megabits

引用自 aXauce：

Going off of steams UI its megabits

if Steam is showing megabits, then 350 Mbps is only about 43 MB/s, which is really slow for an NVMe. Steam's unpacking process is normally slower than raw write speeds because it deals with tons of small files, but 43 MB/s still points to something holding things back.

It's usually stuff like antivirus scanning every file, the SSD throttling from heat, outdated NVMe firmware or drivers, the M.2 slot sharing bandwidth, or the drive being encrypted/compressed by Windows.

Could u open Resource Monitor while unpacking and see what's hitting the disk, run CrystalDiskMark and share the results, check the SSD temperature during the unpack, and maybe exclude ur Steam folder from antivirus or try unpacking to another drive. That should give a clearer picture of what's slowing it down.

How much free space does it have ? temp could throttle the drive .

引用自 smallcat：

How much free space does it have ? temp could throttle the drive .

What do u mean?

Did a CrystalDiskMark run and the max temp a core got up to was 68 degrees (Celsius) at 100% load

CPU Single: 11838 Multi: 149175
Disk Sequential Read: 22660 Random Read: 681 Sequential Write: 22577 Random Write: 2450
2D Text: 10044 Square: 20325 Circle: 18982 Image: 18733
3D Title: 100 Break: 100 WireFrame: 6138 Polygon: 68943

Whilst unpacking steam uses 50 threads and between 0.30 and 0.54 Average CPU and my steam folder has been exempt from steam folder ever since I had this problem in the first place.

引用自 ArielNugie：

引用自 smallcat：

How much free space does it have ? temp could throttle the drive .

What do u mean?

Ops, sorry. When I replied earlier, I didn't check who wrote it, so the question caught me off guard. I thought the OP was suddenly asking me question. Just ignore the reply above

引用自 aXauce：

Did a CrystalDiskMark run and the max temp a core got up to was 68 degrees (Celsius) at 100% load

CPU Single: 11838 Multi: 149175
Disk Sequential Read: 22660 Random Read: 681 Sequential Write: 22577 Random Write: 2450
2D Text: 10044 Square: 20325 Circle: 18982 Image: 18733
3D Title: 100 Break: 100 WireFrame: 6138 Polygon: 68943

Whilst unpacking steam uses 50 threads and between 0.30 and 0.54 Average CPU and my steam folder has been exempt from steam folder ever since I had this problem in the first place.

What about free space? If the drive is close to full, the SLC cache can run out and the write speed during Steam’s unpacking can drop

CrystalDiskMark tests only SSD , at least i think so . seq read/write 22660/22570 i suppose it s in Mbits/s i.e. 2832/2821 MB/s .Look fine

I still had 202GB free before downloading and unpacking and now I'm on 134GB

引用自 aXauce：

I still had 202GB free before downloading and unpacking and now I'm on 134GB

Everything looks normal so far. What about the SSD temp? You mentioned a 'core' hitting 68 degrees, so I’m assuming that was your CPU and not the SSD.

SSD temp gets to 58 degrees

引用自 aXauce：

SSD temp gets to 58 degrees

Your SSD seems fine to me. It's probably just steam's small-file unpacking workload, which is way more random-I/O heavy than normal writes.

引用自 ArielNugie：

引用自 aXauce：

SSD temp gets to 58 degrees

Your SSD seems fine to me. It's probably just steam's small-file unpacking workload, which is way more random-I/O heavy than normal writes.

Is there anyway to get around this? I have friends who unpack the same things in minutes when it takes me hours