#Configure fancycache for a ssd .dll#
#Configure fancycache for a ssd windows#

Sure, the thing will wear out relatively soon, but imagine having the editing and transcoding processes reading and writing data at SSD speeds. Here's a heresy: If the app is using all available memory efficiently, put your video files on a (large) SSD.

Some people actually put in extra memory and create a memory drive, then designate that memory drive as the scratch drive for the app. Data that is never swapped to a drive scratch file, be it SSD or hard drive, will slow things down. The best bang for the buck is more memory if the app can use it. Even if it does make the drive wear out sooner, you will get much more bang for your buck when not only does your program load faster but your images transcode faster too. If you want the process to run faster, put those scratch spaces on the SSD (buy a larger one). Many programs that process large amounts of data, such as video editing, use large scratch spaces on disk. That understanding is that TRIM, garbage collection, and 4 KB alignment are sufficient to maintain performance at near-peak levels until cells start dying from wear. The following suggestion is based on my understanding of the working of a properly fed and cared-for SSD. So I'm thinking that 64 GB may be tight in a year or so.

For Vista, uSoft released a tool to purge the files needed to rollback SP1, but XP doesn't have it. Yes, you can now rollback SP1, but if you don't intend to, you have a lot of space that I consider wasted. Apply an 8 GB patch, you use up 8 GB of space, since nothing is purged as being an old version.

#Configure fancycache for a ssd .dll#

The 'problem' is the solution to 'DLL Hell,' in which all versions of a given dll are stored in the 'Side by side' directory, /windows/winsxs. Installing SP1 brought me up to about 38 GB, and I had to resize the partition. Other points: My 40 GB partition (on my 128 GB SSD) was big enough for Win7 and a few apps.

#Configure fancycache for a ssd windows#

'Used:' Only Windows 7, and the motherboard chipset set to AHCI controller mode, and the drives not in a RAID set, so that the TRIM command will go through. 'Built:' It should support TRIM and ideally garbage collection. In regards to performance degradation from video editing, I disagree.ДЎ) If the OS is installed on the SSD, the video data and application scratch area are on the hard drive(s), and there is enough physical memory to minimize swapping, the massive IO of video editing won't be on the SSD.Дў) Large amounts of activity to the SSD will not, on a properly built and used SSD, degrade performance. Had to remove 4 fans to get that monster in and replace with very loud high CFM fans to keep cool, but in spare bedroom and I hear nothing as I have everything routed to my HDTV in the livingroom. Do I need to get rid of one or two? I have a Antec NEW Truepower 750 modular pushing everything with a Noctua NH-D14 sitting on top my 965 that is in the way of everything. And is there such a thing as having too many HDD's? I have a 2 TB, 500GB, 320Gb, and adding 128 SSD. I get a Heaven benchmark 2.5 of 943 running it this way and just want games and OS on SSD, well a couple utilities as that is all the room I can afford now that I have to pay for this monster. My ASUS mobo M4A88TD-V EVO USB3.0 SATA III 6.0 with a Phenom II 965 OC'd to 4.0 and Kingston Value ram OC'd to 1600 with 2 Sapphire HD 5770's OC'd to 950 clock. My question is can I set up a raid configuration using my new SSD as primary and the Hitachi partitioned off in RAID? Would it be something like 0,1? And will this just slow everything down to where I will not benifit from the SSD at all. The hitachi is only as fast as the platters spin at 7200 rpms and you get no faster data rate as if it were SATA II. I am putting in a new SSD 128 GB SATA III 6.0 and bought a Hatachi 2 TB 6.0 for my new build thinking it would speed right along.