Page 3 - DC - Timings & the 32-bit memory hole

Dual Channel memory ?

Always make sure you buy two bars so that you can have a dual-channel memory configuration (typically color coded identically on your mainboard). Dual channel effectively double's the memory bandwidth and processors loves that bandwidth, for sure, as it can have a nice impact on overall performance.

So keep this in mind: performance and stability of any system depends in part on the memory being used and the settings for the RAM timings. Many users may have their preference for low-quality class-B brands; but certainly using brand name memory is a very good idea since low quality memory is often at the root of many stability issues. However, always pay attention to the timings of the memory being used.

What are memory timings ?

Let's explain a little what you will run into with memory timings. First off latency. We used the word numerous times already in this article. Latency is the time between when a request is made and the request is answered. I.E, if you are in a restaurant for a meal, the latency would be the time between when you ordered your meal to the time you received it. Therefore, in memory terms, it is the total time required before data can be written to or read from the memory. Thus lower is better.

Then we notice on the packaging is this: 5-4-4-15 (2T) for the OCZ2N800SR4GK 2 GB kit. What do the numbers mean ?

Well, lets take that sequence... 5-4-4-15 (2T), this refers to CAS-tRCD-tRP-tRAS CMD (respectively) and these values are measured in clock cycles.

CAS Latency
Undoubtedly, one of the most essential timings is that of the CAS Latency and is also the one most people can actually understand. Since data is often accessed sequentially (same row), the CPU only needs to select the next column in the row to get the next piece of data. In other words, CAS Latency is the delay between the CAS signal and the availability of valid data on the data pins (DQ). Therefore, the latency between column accesses (CAS), plays an important role in the performance of the memory. The lower the latency, the better the performance. However, the memory modules must be capable of supporting low latency settings.

tRCD
There is a delay from when a row is activated to when the cell (or column) is activated via the CAS signal and data can be written to or read from a memory cell. This delay is called tRCD. When memory is accessed sequentially, the row is already active and tRCD will not have much impact. However, if memory is not accessed in a linear fashion, the current active row must be deactivated and then a new row selected/activated. It is this example where low tRCD's can improve performance. However, like any other memory timing, putting this too low for the module can result in instability.

tRP
tRP is the time required to terminate one one Row access and begin the next row access. Another way to look at this it that tRP is the delay required between deactivating the current row and selecting the next row. Therefore, in conjunction with tRCD, the time required (or clock cycles required) to switch banks (or rows) and select the next cell for either reading, writing or refreshing is a combination of tRP and tRCD.

tRASMemory architecture is like a spreadsheet with row upon row and column upon column with each row being 1 bank. In order for the CPU to access memory, it must first determine which Row or Bank in the memory that is to be accessed and activate that row via the RAS signal. Once activated, the row can be accessed over and over until the data is exhausted. This is why tRAS has little effect on overall system performance but could impact system stability if set incorrectly.

Command Rate
The Command Rate is the time needed between the chip select signal and the when commands can be issued to the RAM module IC. Typically, these are either 1 clock or 2.

Memory testing is a process of trial and error, find and seek the maximum. This is pretty much a sucker for your free time.

If you are going to overclock then increase the FSB, change the memory timings, but most of all alter memory dividers until your system won't boot. If you are not comfortable with such a thing, hey this isn't your game then. I recommend you to lower the processor's multiplier and then slightly increase the FSB with high memory timings and take it from there timings wise.

Fact is that today's Intel processors really are dependant on memory bandwidth, the faster the better. Something that is by far not as important for AMD processors.

Why Gigabytes of memory?

Windows 98, who didn't use that OS? What amount of memory did your PC have? Right, likely 128 MB.

Over the years we progressed and noticed that applications have gotten more and more memory intensive. With Windows XP we moved towards 512 MB as standard to prevent the OS from swapping to the HD, and as explained on the previous page with the latest games we see that the certain games really like 1 GB. All this has happened over just a couple of years my friends.

Then Microsoft launched Windows Vista, the biggest memory hog in the world. 1 GB is just be the average recommended specification. They actually recommend 2 GB. See... 2GB isn't that special anymore. But with memory prices coming down you might even consider taking it a step further.

OCZ Technology

The OCZ 4GB PC2-6400 DDR2 DIMM Dual Channel Kit memory we'll be testing today is two bars of 2 GB (in dual channel mode you gain the best memory bandwidth). The modules are tagged under SKU number OCZ2N800SR4GK and have some pretty brave 5-4-4-15 timings (for 2x2GB DDR2 memory) at 800 MHz. For four GB of memory these are really nice timings. It's SLI Ready (EPP enhanced) memory, meaning that the mainboards that support it (EPP), can read out pre-set configuration from the memory for optimal timings. Do it like I do though, set it manually, please.

Each of the OCZ SLI-Ready module comes equipped with a (as the photo's will show) NVIDIA XTC heatspreader for the good heat dissipation and a look more importantly, aesthetics. Also worthy to mention, all SLI-Ready memory is backed with toll-free technical support, the EVP (Extended Voltage Protection) coverage, and (and I really do love this) comes with a Lifetime Warranty.

I'm on a 32-bit Operating system.
Dude, where's My 4 Gigabytes of RAM?

Can I use 4 GB of memory ? Yes and no. As far as 32-bit Vista is concerned, the world ends at 4,096 megabytes. That's it. 4GB will run just fine, yet with for example Windows Vista 32-bit your memory size will be limited and you'll only have 3.2 GB out of the 4 GB available to you. This isn't a Windows problem-- it's an x86 hardware problem.

To address 4GB of memory you need 32 bits of address bus. There however is a problem - actually a similar problem that IBM faced when designing the original PC. You tend to want to have more than just memory in a computer - you need things like graphics cards and hard disks to be accessible to the computer in order for it to be able to use them. Microsoft call this MMIO (Memory-Mapped I/O).

For example, if you have a video card that has 256 MB of onboard memory, that memory must be mapped within the first 4 GB of address space. If 4 GB of system memory is already installed, part of that address space must be reserved by the graphics memory mapping. Graphics memory mapping overwrites a part of the system memory. These conditions reduce the total amount of system memory that is available to the operating system.

So just as the original PC had to carve up the 8086's 1MB addressing range into memory (640K) and 'other' (384K), the same problem exists today if you want to fit memory and devices into a 32-bit address range: not all of the available 4GB of address space can be given over to memory.

For a long time this wasn't a problem, because there was a whole 4GB of address space, so devices typically lurk up in the top 1GB of physical address space, leaving the bottom 3GB for memory. And 3GB should be enough for anyone, right?

So what actually happens if you go out and buy 4GB of memory for your PC? Well, it's just like the DOS days - there's a hole in your memory map for the IO. (Now it's only 25% of the total address space, but it's still a big hole.) So the bottom 3GB of your memory will be available, but there's a discrepancy with that last GB. If you want it all, go with a 64-bit OS. In 64-bit Windows, the limit is gone.

Anyway, let's have a peek at the modules and throw them at a test.