Navigate:

Advice
Beginners
BIOS Guide
CPUs
Links
Mainboards
Memory
Network
Storage
Video/Sound Cards

Contact
Forum
SiteMap
Sponsors
WebNews
Home
. .

Prices:

Mainboards

ABIT
ASUS
Chaintech
Shuttle
Soyo
Tyan



CPU
Intel
P4 2.4C-800
P4 2.6C-800
P4 2.8C-800
P4 3.0-800
P4 3.2-800

AMD
AthlonXP
XP 1700+
XP 2000+
XP 2400+
XP 2500+
XP 2700+
XP 3000+
XP 3200+

Athlon64
Athlon64 3200+
Athlon64 FX-51

Opteron
Opteron 240
Opteron 242
Opteron 244
Opteron 246

Memory

Corsair
Crucial
Kingston
Mushkin
OCZ

Search Prices:










































































LOSTCIRCUITS

SHORTCUTS:
Top Page
Caching and MaxBoost
DiamondMax Plus 9
Basic Performance
MaxBoost
WinBench99
WinBench99 + MaxBoost
Seek, Average Random Transfers
The Poodle's Core

Barracuda 7200.7 - 160 GB
On Dealtime

Please give us some feedback to help us improve our reviews

 Maxtor DiamondMax Plus 9
160 GB and SATA
(Review by MS, January 2, 2004)
Maxtor DiamondMax
Plus 9 6Y160M0
160 GB SATA 1.5

Read/ Write/Caching and MaxBoost

Any mass storage media such as HDDs have to be able to perform READ and WRITE operations and all current standards are using caching schemes as well. In the case of READs, barring prefetch and read-ahead, there are currently no real strategies involved, the data can only be read in the sequence they are requested and the platters are "dumb" media. The situation is entirely different when it comes to writing data back to the media. First, the data can be managed within the drive's cache, meaning that if there are data that are continuously modified / updated, those updates can occur in the cache and only the final version will be written to the media - a strategy often referred to as "lazy writes".


The drawback of cached writes is that any critical system failure can cause the data to be lost before they are written to the media. Candidates for this scenario are system malfunctions caused by program crashes as well as the ubiquitous power outage. In this case, often the metadata (data that describe the real data) are already updated, however, the real updated data are lost. Consequently, there are mismatches and / or errors, which is the reason why in e.g. Windows 98SE and WindowsXP the write cache is disabled by default, instead, "forced unit access" (FUA; direct write to the media) is used. Alternatively, in high-end solutions, non-volatile memory like, for example, NVSRAM can be used for journaling (keeping track of what has been written and what has not).

A different strategy for writes is to write all data to a dedicated area within the system memory and then schedule them for the most economic write pattern to the drive. It is a very straightforward strategy utilizing part of the system memory as dedicated write cache. An additional advantage is that any further modification of the data will not even have to access the drive itself but can be executed in memory within the resident copy of the data and the drive will be updated whenever it is necessary. In other words, what we are looking at is the equivalent of a RAM-disc or the reversed principle of the "Virtual Memory" strategy where the HDD needs to handle the data overflow in case there is not enough system memory available.

In that case, the "virtual drive's" data bandwidth will be similar to the memory bandwidth, which is an order of magnitude higher than what even the fastest drive can accomplish. The data on the HDD media are updated at the rate supported by the drive itself, however, data access itself, since it occurs from memory will bypass the drive itself completely and, therefore, be ultra fast. Issues associated with this strategy are first, the same problems as with caching data in non-volatile memory, namely the risk of data loss and, second, the fact that only recurrent data can be cached. On the other hand, using system memory as write buffer allows more efficient use of data, in other words, the data transfer to the drive itself is not influenced to the same degree by interrupts and PCI latencies or bus bottlenecks as in the case of a standard configuration. Overall, it is a nifty concept but, as outlined above, not without risks. The question is, how much of a difference does it actually make in terms of real world performance.

next page:    => Maxtor DiamondMax Plus 9 =>

All advice and educational articles on LostCircuits are free, but if you feel you can, please make a small donation to us!
Thank you!

General disclaimer: This page only reflects the author's personal opinion and assumes no responsibility whatsoever regarding any of the contents or any damages that may occur explicitly or implicitly from reading the contents of this site. All names and trademarks mentioned in this review are the exclusive property of the respective parent companies.
All contents of this site are protected by international copyright laws. Reproduction of the contents even in parts is not allowed except after written permission by the author and referral to this site.
Copyright 2002 - 2007 LostCircuits