Surface Pro 4 SSD

[netmann]

I happened to be at a MS Store yesterday and took the photo below in the Device Manager:

I am curious to find out the Samsung SSD specs in the casing. Google search did not find much. Can anyone identify the SSD? Perhaps a Samsung employee can shed some light on this!

I would like to know the following:

1. Is it PCI base M.2 format or mSATA?
2. IF PCI, Is if PCI3 4 lanes or 2 lanes?
2. Maximum MB/s read speed?
3. Maximum MB/s Write speed?

Thanks

 

[xboxonthego3]

I wonder if it is actually this SSD from Samsung. NVMe in M.2 format is fairly new Samsung SM951 NVMe M.2 PCIe 256GB SSD Review

 

[DCProjMgr]

The units shipped out to reviewers had the 256 GB Toshiba XG3 SSD. It is Toshiba's high performance model, using the m2 PCIe 3.1 x4 NVMe interface.

 

[netmann]

Since my original message SP4 review went viral. Storagenewsletter report the SSD to be Toshiba NVMe XG3 with the following specs:

Maximum sequential read speed: 2516 MB/s
Maximum sequential write speed: 1572 MB/s

Anandtech review showed the following:

Sequential read speed: 1494 MB/s
Sequential write speed: 555 MB/s


The max values are what the SSD can handle which is pretty impressive. Unfortunately, Anandtech testing values appear to show that Microsoft and/or Toshiba have put a speed cap on the true speed of this SSD!!!?

 

[CygnusOrion]

Since my original message SP4 review went viral. Storagenewsletter report the SSD to be Toshiba NVMe XG3 with the following specs:

Maximum sequential read speed: 2516 MB/s
Maximum sequential write speed: 1572 MB/s

Anandtech review showed the following:

Sequential read speed: 1494 MB/s
Sequential write speed: 555 MB/s


The max values are what the SSD can handle which is pretty impressive. Unfortunately, Anandtech testing values appear to show that Microsoft and/or Toshiba have put a speed cap on the true speed of this SSD!!!?

I wonder if that's to keep the system within a thermal envelope.

 

[netmann]

I wonder if that's to keep the system within a thermal envelope.

I doubt that's the reason. I think it is the limited MS drivers for NVMe protocol.