Apacer reveals its PCIe Gen 5 NVMe SSD with 13,000MB/s read speeds

Apacer reveals its PCIe Gen 5 NVMe SSD with 13,000MB/s read speeds

For those hoping for faster SSDs, PCIe Gen 5 NVMe SSDs for PCs are coming this year, and that’s good news if you own a compatible Alder Lake motherboard or plan to get one with AMD socket AM5. ANDAt Computex 2022, Apacer has announced two such storage solutions, both of which offer transfer speeds of up to 13,000 MB/s.

The first of the two SSDs, the AS2280F5 M.2 PCIe Gen5 x4 SSD, is compatible with the latest NVMe 2.0 standard and backwards compatible with PCIe Gen 4, but you’ll need to connect it to a PCIe 5.0 compatible board. to reach read speeds of 13,000 MB/s and write speeds of up to 12,000 MB/sdouble what the PCIe 4.0 connection offers.

The SSD features an aluminum heat sink and multiple protection technologies to ensure data accuracy and stability.

Read This Now:   AMD like NVIDIA? Dedicated hardware on future Radeons to handle upscaling?

They achieve read speeds of 13,000 MB/s and write speeds of up to 12,000 MB/s.

Next up is the Zadak TWSG5 Gen5 x4 SSD. It has most of the specs of the AS2280F5, including read/write speeds and Gen 4 compatibility, but offers two types of heat sinks: graphene, which is ultra-thin, and aluminum.

No word on drive capacities or pricing, but you can expect the price at launch to be similar to or more than PCIe 4.0 SSDs, obviously. Both come with a five-year warranty.

AMD, which has revealed a lot of details about its Zen 4 architecture during Computex 2022, and has confirmed that the first PCIe 5.0 SSDs will arrive alongside its new platform later this year. The company is working with various manufacturers, including Apacer, to ensure they are ready on time.


Notice: ob_end_flush(): failed to send buffer of zlib output compression (1) in /home/gamefeve/bitcoinminershashrate.com/wp-includes/functions.php on line 5420

Notice: ob_end_flush(): failed to send buffer of zlib output compression (1) in /home/gamefeve/bitcoinminershashrate.com/wp-includes/functions.php on line 5420