Warning: Always look at the date when you read a hardware article. Some of the content in this article is most likely out of date, as it was written on June 29, 2012. Check out our more recent articles.
SSD caching (also known as Intel Smart Response Technology) is not new, but is something we have not inspected closely since its introduction with the Z68 chipset. SSD caching is intended to provide improved performance for computers that use traditional hard drives in a way that is both cost effective and easy to configure. This is done by using a small, relatively cheap SSD drive to cache or store commonly accessed data. Since SSDs are much faster than traditional hard drives, this allows the computer to read the cached data much faster than if it had to read the same data directly from the hard drive.
SSD caching reduces the time it takes to load commonly used programs, but there is a limit to the benefits. If the data is already stored in the computer's RAM, then SSD caching does not improve load times at all since the computer's RAM is much faster than even the fastest SSD drive currently on the market. The main advantage of SSD cache comes into play when booting into Windows or when a program is run for the first time after a reboot or power off. Since the data in RAM gets cleared each time the computer powers cycles, the data is not present in the RAM whereas it is still present on the SSD cache drive.
With SSD caching setup and configured, all that the cache needs in order to function is for the program to run once. After that, the data is stored for future access within the cache drive. On a chipset level, Intel SSD caching is currently only compatible with certain chipsets and their mobile equivalents, but some motherboard manufactures have released software that does much the same thing as Intel SSD caching. In this article we will only be examining the performance of the SSD caching as provided directly from Intel.
In order to understand SSD caching and how it works, you need to understand some of what is going on behind the scenes when a computer is trying to find the data it needs. When a program is first run, all of the different files needed to launch that program (the main .exe, dll files, etc.) are read from the hard drive and loaded into the different levels of temporary storage found in a computer. On most computers, the basic hierarchy goes:
Due to space limitations, not all of the data in a computer can be stored into the relatively small CPU cache or RAM, and SSD caching is no different. While the algorithm to decide what data gets cached is confidential, our testing shows that at the very least, files larger than a few MB are not stored in the SSD cache.
Setting up an SSD cache is very easy as long as the following requirements are met:
Before we get into actually setting up SSD caching, there are a few things to note: First, a platter hard drive is required since the benefits of SSD caching are completely non-existent if you already using a SSD as your primary drive. Second, SSD caching is limited to 64GB. If the SSD is larger than 64GB, the remaining space is partitioned as a standard drive. You can either leave this space empty, or format it for use as additional storage through Window's Disk Management utility.
Once the five requirements listed above are fulfilled, simply follow the four easy steps shown below to enable and configure SSD caching:
**Maximized Mode: Acceleration optimized for input/output performance. This mode uses the write-back cache method where data is written to the disk at intervals. In the event that the cache device or the accelerated disk or volume becomes inaccessible or disconnected, there is a chance of data loss. However, if the device was missing and can be reconnected, reboot your system and caching activity will resume from where it stopped. If you wish to remove the cache device in the future, make sure that acceleration is first disabled on that disk or volume.
To test the performance benefit of SSD caching, we used the following hardware in a laptop system:
To benchmark the performance advantages, we decided to start off with testing the difference SSD caching makes to Window's boot times. To do this, we used BootRacer to record how long it took Windows to load in each of our configurations. BootRacer provides measurement from two different points: when the base OS is loaded and ready to start user-specific applications; and when the OS is fully loaded and completely ready to go. We went ahead and provided both readings, although the total is what most readers will likely be interested in. Note that these results are only for the Windows boot time and do not include pre-boot actions such as POST or BIOS hardware detection.
Sufficed to say, we were very impressed with the results. Our boot times were only 60% of what they were without SSD caching and essentially identical to simply using the SSD as the boot drive. The only unexpected result was that the difference between Enhanced and Maximized caching modes was so little. Given the risks associated with using Maximized cache, we highly recommend using the Enhanced cache setting if your primary goal is to improve Windows boot times.
Moving on to our application load testing, we ran three different programs and recorded how long it took for each to fully load: GIMP (image editing), Avid Studio (video editing) and Google SketchUp (3D modeling). This is a fairly limited number of programs, but we wanted to cover the basic idea of SSD caching across in this article, and not get too caught up on how SSD caching improves performance on a per-application basis.
Each of the programs had been previously launched (so that they would be present in the SSD cache when available) but the system was rebooted before taking our measurements to ensure that they were not simply running from the computer's RAM.
While it is impossible to define a trend using so few data points, our results appear to show that the longer a program normally takes to load, the greater the benefit gained from using SSD caching. With load times reduced to 25-35% of the standard load times, it's clear that SSD caching is not just a hype tool, but is very useful in minimizing load times.
What really surprised us was how well the SSD caching performed compared to having the OS running directly from the SSD. Having the OS and programs installed directly onto the SSD provided a bit better load times, but the results were close enough that we completely validated Intel's claims of getting SSD-like performance by using SSD caching.
The testing we performed for this article just barely scratches the surface of the various programs that can benefit from using SSD caching. If you want to learn more about the performance benefits of SSD caching, we recommend checking out the Anandtech and Tom's Hardware articles about Intel SSD caching. These articles are a little bit dated, but the technology for SSD caching has not changed much since the launch of Z68 so they are still very valid.
Overall, we were very impressed with how much OS and program load times were reduced when using SSD caching. One thing to keep in mind, however, is that using SSD caching does not result in a system-wide increase in performance. Reading data over a few MB in size and writing data must still be done directly from the hard drive and will not benefit from having an SSD as a cache drive. Depending on the size of the cache drive, some data might also get "evicted" from the cache as you continue using your computer and newer data gets written to the cache drive.
So really, whether or not SSD caching is right for you depends on what you use your computer for. Do you spend most of your time opening lots of different programs, but rarely any large files? If so, SSD caching will likely give you a very nice performance boost. Or, do you spend your day reading and saving very large files? In that case, SSD caching will still give the performance boost when opening programs, but the actual reading and writing of the files will not be any faster. At the very least, Windows load times will be greatly improved no matter what your computer is used for.