Owners Manual
Table 5. Memory specifications (continued)
● 32 GB - 4 x 8 GB
● 64 GB - 4 x 16 GB
Type ECC/Non-ECC memory
Speed 2666 MHz
NOTE: Pentium and i3 will run at 2400 MHz
Storage
Table 6. Storage specifications
Type Form factor Interface Security option Capacity
One NVMe Solid-State
Drives(SSD)
M.2 2280 PCIe 4, Up to 32 Gbps SED Up to 1 TB
One Solid-State Optane
memory drive (SSD)
M.2 2230 PCIe, Up to 32 Gbps
32 GB
Two 2.5 inch Hard-Disk
Drive (HDD)
Approximately (2.760 x
3.959 x 0.374 inches)
SATA AHCI, Up to 6
Gbps
SED, Opal, FIPS Up to 4 TB
One 3.5 inch Hard-Disk
Drive (HDD)
Approximately (2.760 x
3.959 x 0.276 inches)
SATA AHCI, Up to 6
Gbps
Up to 4 TB
Table 7. Storage configurations
Primary/Boot drive Form Factor
1 x M.2 Drive NA
1 x M.2 Drive 1 x 2.5 inch Drive
1 x 2.5 inch Drive NA
1 x 2.5 inch HDD NA
1 x Slim Optical Disk Drive CAC/PIV - Common Access Card/Personal Identification
Verification - CAC/PIV
NOTE: Supports RAID 0 and 1 with dual 2.5 " HDD. It is not available with Optane memory (Available from August 2019).
For optimal performance when configuring drives as a RAID volume, Dell recommends drive models that are identical.
RAID 0 (Striped, Performance) volumes benefit from higher performance when drives are matched because the data is split
across multiple drives: any IO operations with block sizes larger than the stripe size will split the IO and become constrained by
the slowest of the drives. For RAID 0 IO operations where block sizes are smaller than the stripe size, whichever drive the IO
operation targets will determine the performance, which increases variability and results in inconsistent latencies. This variability
is particularly pronounced for write operations and it can be problematic for applications that are latency sensitive. One such
example of this is any application that performs thousands of random writes per second in very small block sizes.
RAID 1 (Mirrored, Data Protection) volumes benefit from higher performance when drives are matched because the data is
mirror across multiple drives: all IO operations must be performed identically to both drives, thus variations in drive performance
when the models are different results in the IO operations completing only as fast as the slowest drive. While this does not
suffer the variable latency issue in small random IO operations as with RAID 0 across heterogeneous drives, the impact is
nonetheless large because the higher performing drive becomes limited in all IO types. One of the worst examples of constrained
performance here is when using unbuffered IO. To ensure writes are fully committed to non-volatile regions of the RAID volume,
unbuffered IO bypasses cache (for example by using the Force Unit Access bit in the NVMe protocol) and the IO operation will
not complete until all the drives in the RAID volume have completed the request to commit the data. This kind of IO operation
completely negates any advantage of a higher performing drive in the volume.
12
System specifications