Originally Posted by Bonn93
Ahh didn't see they were SATA2. It still won't make much of a difference as it's a cache drive, it's only there as it can read and write faster to ram from the SSD, so it would do the job, I think a full blown Toggle NAND SATA3 SSD is overkill as Cache.
BTW its Ca-shE! not CASH drive, silly americans!
Intel cache will make full use of the SSD speed and will expose weaknesses in lower performing drives. There are benchmarks showing that Intel Cache can end up being barely faster than a normal drive if the SSD is not up to par. There are also plenty of reviews and benchmarks that show it will stomp on a normal drive in program load and OS load times once the program has been run at least 2 times already (if it is a good SSD). So the first time you load a video game or an area of a game it will be no faster than the HD it is attached to. The second time it will be a little but not much faster the third time it will be difficult to discern the difference between that SSD on it own vs it paired via Intel Cache it would be 70-99 percent the performance in comparison to that program being JUST on an SSD by itself. There are 2 ways I could figure that it would actually do better but I can't prove them and I doubt this is the actual way it works but it could be possible. Intel could be reading from both the SSD and the HDD the 3rd time around which could possibly increase the max read speed but not the seek speed so increases could be negligible but it could actually be possible to go over 100% performance (unlikely scenario though). The other much more likely scenario is that if you fill an SSD close to it's max it will slow down a lot... Intel is aware of this but if that knowledge that has been implemented into the control firmware and software then the software would make sure not to allow that to happen meaning you don't have to worry about the cache mode but if you used that drive on it own it would already be bloated with garbage and could slowly reduce the performance on the drive.
So it matters a lot which SSD you buy.
Also as far as it being difficult to divide part of it as cache and part of it as something else that isn't really true or I should say it is absolutely false. It is handled in part by the on board raid controller and part by the software. You must enable it via the software in windows but once that is done you will see the drive in the raid controllers bios as being a cache drive.
"Any remaining space on the SSD may be used for data storage using the simple data single-disk RAID 0 volume that is automatically
Automatically as in all you have to do is format it and throw stuff on it.
I did not remember this but... You can either use 18.6GB of the SSD or all of the SSD up to 64GB nowhere in between! So if you have a 40GB you can use 18.6GB or 40GB. If you have a 128GB you can use 18.6 or 64GB. If you catch my drift. In other words you can not use 40GB of a 128GB drive.
So if you buy a 64GB I would use all of it... If you buy a 128... well then it ends up being a harder decision. On one hand you get the max performance of the Intel Cache system on the other hand you get a lot more storage on the left over partition. Intel said themselves that over a certain amount (I think 20GB) the cache system does not get significantly better because it is already very optimized. You just don't access a lot of what actually gets installed with windows and other applications and since it will only be caching the stuff that needs to be cached it doesn't make a major difference to have a much larger cache drive.
I do not know if that statement holds true when enabling write caching which by default is not enabled BUT write caching would not take up much space at all since from my understanding all write caching does is write a small amount of data to the SSD once a certain amount of data is hit the caching stops or slows down to the speed of the HDD until the extra data can be written to the HDD. That may be a safety feature I am not sure why it works that way but that is how I noticed it worked.
For example if you write a several hundred MB file to the main drive it will write it at SSD speed. If it is several GB it will start writing it at SSD speed and then suddenly it will go down to HDD speed. This is more important when the computer is actually creating a file (which is rarely several GB) than when transferring a file from one drive to another because unless the other drive is an SSD then it is going to be limited to ~100MB/s anyways unless it is a raid array.
Also to give you an idea of how much room windows wastes I have used RT7Lite and the other program like it to reduce the install size of Windows Vista and 7 by about half without loosing any major functionality. Even at half you still are not actually loading nearly any of that... To give you a better idea there have been people that have made successfully running copies of Windows 7 that only take 2-3GB of HDD space and still retain the majority of it's functionality.
The same thing is happening in your video games and stuff like downloads, game updates, windows updates, junk files you don't know about etc do not need to be on an SSD and if the SSD is your primary drive well you often don't even know that there are files just being thrown on without your consent that don't get deleted later. Especially with games that use P2P for the update files since they store the files in your game folder and sometimes never delete them. (Intel cache does not cache these files unless they are ran multiple times and are not media)
In other words... using the full 64GB may not be that big of a deal but I don't know for sure because I always used the max amount I could and the smallest drive I ever used was 40GB.Edited by givmedew - 6/24/13 at 2:10am