c1e support - enabled
max cpuid - enabled (I think...this is the thing that lets you change the ratio, right? If so, then enabled)
vanderpool - enabled
cputm - disabled
peci - left at whatever the default is
EIST is SpeedStep, I think. It's like AMD's Cool'n'Quiet, where it tries to tweak your closk speed on the fly to reduce heat/power consumption. I leave it disabled since I'm overclocking anyways, though I'm not sure if it's detrimental to overclocking by itself.
And also, the computer has been resurrected. Everything reinstalled and reconfigured and working great (and 0 viruses this time). I also had time to install a few other games, and also set up my development environment and run a handful of tests, and for work-related things the new system is between 2 and 3 times faster than the system it is replacing (starts the server in half the time, builds the workspace in a bit under half the time, loads the databases in 1/3 rd of the time), and for games it is much faster as well (hard to tell exactly what the scale-factor is, since I'm running at higher resolutions with higher detail levels and still getting smoother performance than the previous system). Overall it seems to be a very successful build.
Edit: One other thing I noticed, the write performance on the RAID-5 seems to be very poor (seems to take about 2.5 minutes to transfer 1 GB of data onto it, even when the source is capable of going much faster than that). I had a seperate 2.5 GB partition on it for my pagefile, but had to move it to the RAID-0 because whenever the system had to page things it would slow down noticeably. After moving it, I can't even tell if/when the system is paging anymore. Read performance of the RAID-5 is great though, and since it's only meant to hold multimedia and other read-only/read-mostly data, it's okay if writing is slow. Still, I wonder if it's a bug in the driver, or if RAID-5 really is that slow for writing data (my CPU usage only shows as 2% when writing to it, so maybe it's being underutilized for the parity calculations).
max cpuid - enabled (I think...this is the thing that lets you change the ratio, right? If so, then enabled)
vanderpool - enabled
cputm - disabled
peci - left at whatever the default is
and also what is EIST i see people disabling this feature
EIST is SpeedStep, I think. It's like AMD's Cool'n'Quiet, where it tries to tweak your closk speed on the fly to reduce heat/power consumption. I leave it disabled since I'm overclocking anyways, though I'm not sure if it's detrimental to overclocking by itself.
And also, the computer has been resurrected. Everything reinstalled and reconfigured and working great (and 0 viruses this time). I also had time to install a few other games, and also set up my development environment and run a handful of tests, and for work-related things the new system is between 2 and 3 times faster than the system it is replacing (starts the server in half the time, builds the workspace in a bit under half the time, loads the databases in 1/3 rd of the time), and for games it is much faster as well (hard to tell exactly what the scale-factor is, since I'm running at higher resolutions with higher detail levels and still getting smoother performance than the previous system). Overall it seems to be a very successful build.
Edit: One other thing I noticed, the write performance on the RAID-5 seems to be very poor (seems to take about 2.5 minutes to transfer 1 GB of data onto it, even when the source is capable of going much faster than that). I had a seperate 2.5 GB partition on it for my pagefile, but had to move it to the RAID-0 because whenever the system had to page things it would slow down noticeably. After moving it, I can't even tell if/when the system is paging anymore. Read performance of the RAID-5 is great though, and since it's only meant to hold multimedia and other read-only/read-mostly data, it's okay if writing is slow. Still, I wonder if it's a bug in the driver, or if RAID-5 really is that slow for writing data (my CPU usage only shows as 2% when writing to it, so maybe it's being underutilized for the parity calculations).