Channels ▼


High-Performance Computing: RAM versus CPU

Michael Schulman is the Marketing Manager for High Performance Computing at Sun. He has a BS degree in Civil Engineering from Cornell University, and an MS in Computer Graphics from Cornell University.

High-performance computing (HPC) typically involves running mathematical simulations on computer systems. A few examples of commercial HPC are the simulation of car crashes for structural design, molecular interaction for new drug design, and the airflow over automobiles or airplanes. In government and research institutions, scientists are simulating galaxy creation, fusion energy, and global warming, as well as working to create more accurate short- and long-term weather forecasts.

For most HPC simulations that are run, the CPU instruction mix contains significant amounts of floating-point calculations, and less integer calculations. A principle often associated with CPUs is Moore's Law, which states that the density of transistors that can be put onto a chip doubles about every two years. Recently, the increase in CPU speeds has slowed in terms of single processor performance. Most commercial applications running today do not take advantage of the new multi-core designs, and thus are being over-served by the increasing density associated with Moore's Law. These types of applications just don't need the increase amounts of computing power that is provided today.

Despite this, HPC users are still demanding more performance as they try to solve more complex problems and desire faster turnaround. Other markets demanding more performance include those that are involved with delivering compelling, new content over the Web, and enterprise customers who are expanding their offerings to either employees or customers. Figure 1 illustrates this trend. In this article, I delve further into the concepts and issues surrounding HPC, specifically taking a look at CPU and RAM in relation to HPC.

[Click image to view at full size]
Figure 1: The Redshift

Related Reading

More Insights

Currently we allow the following HTML tags in comments:

Single tags


<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags


<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

