Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Vulnerabilities / Threats //

Insider Threats

11:32 AM
George Crump
George Crump

The Death Of DRAM?

SSD increasingly will be used to replace DRAM in everything from laptops to servers. Here's why that makes sense.

As I flew to the Flash Memory Summit Tuesday, I was thinking about predictions for what the event will mean for the average data center manager. One of the top trends that I think we will see over the next year is the replacement of DRAM with flash-based solid-state drives (SSD) in everything from laptops to servers.

I know SSD is supposed to replace storage, so why start picking on DRAM? Because DRAM is an expensive resource that is hard to install in quantity.

The Laptop Case: The number one reason to consider flash SSD in a laptop, as we have seen in our testing, is that it limits the amount of RAM required in that laptop. Meaning that instead of buying an 8-GB laptop you can buy a 2-GB laptop with SSD. Yes, 2 GB of RAM will mean that the operating system has to use virtual memory and swap pages of memory to storage. Now, though, those page swaps will be to a SSD, not a hard disk drive (HDD). In our testing, the performance difference was almost unnoticeable. If you are looking to upgrade the RAM in your laptop, think about upgrading to SSD instead. Get faster drive performance and faster virtual memory.

Flash memory does not always have to be the size of a mechanical hard drive. Using a flash in a memory-module form factor, instead of a drive form factor, can significantly reduce the size of the system. Drive form-factored SSDs, of course, are ideal for upgrades, but new system suppliers should be considering a memory-module approach. This will allow them to build smaller laptops or use the additional space for a larger battery.

The Enterprise Case: While we almost always focus on the performance aspect of flash SSD in the data center, it should also impact how much DRAM you put in a server. Enterprise SSD is faster than what you would put in your laptop--especially PCIe SSD--so thinking of using it as an alternative to additional server memory can be very realistic. The cost of 64 GB or more of DRAM in a server can add up quickly, and it's also risky since it is volatile.

There is also the physical limit of how much DRAM the typical server can physically hold. Comparatively, PCIe flash cards are all in the 500 GB or more capacity range. If you are counting on your database to leverage memory to improve performance, your chances of a cache hit go up dramatically with a 500-GB flash cache vs. a 128-GB DRAM cache. The same is true for a virtualized infrastructure where the need to send pages of memory to storage is more common and the need for RAM more severe.

Where does this leave DRAM? Ironically it has a significant role in storage. As we discussed in our article The Advantages of DRAM SSD, DRAM still enjoys a significant write-performance advantage over flash SSD, as well as a durability advantage. It makes sense then to leverage DRAM as part of a flash solution so that it can take the brunt of the inbound write traffic and increase the life and performance of the overall storage system.

We have always thought of SSD as expensive storage, needed for high-performance situations. Instead maybe (and especially in the server-based case) we should be thinking of it as cheap and more plentiful DRAM and then use a small amount of DRAM where it makes sense in storage systems managing high-write I/O. In fact, mixing the two memory types (flash and DRAM) may become standard practice, especially in the enterprise.

Follow Storage Switzerland on Twitter

George Crump is lead analyst of Storage Switzerland, an IT analyst firm focused on the storage and virtualization segments. Storage Switzerland's disclosure statement.

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
User Rank: Apprentice
10/26/2011 | 10:34:39 PM
re: The Death Of DRAM?
There are some new things to do with DRAM, like embedding CPUs in it.

see p.10 for Sandia Labs MapReduce benchmarks.

Russell Fish
[email protected]
COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
The State of Ransomware
The State of Ransomware
Ransomware has become one of the most prevalent new cybersecurity threats faced by today's enterprises. This new report from Dark Reading includes feedback from IT and IT security professionals about their organization's ransomware experiences, defense plans, and malware challenges. Find out what they had to say!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.