Windows 7 SSD Settings

Associate
Joined
31 Jan 2009
Posts
952
Location
London
Morning! I am just awaiting delivery of my new Intel X25-M SSD!

Just wondering if there are any settings I need to configure to make sure I get maximum performance?

I've heard a lot about TRIM, stripe sizes, defragging etc but I'm not really sure if I need to change them in win7 or if it's set up automatically.


Many thanks
 
yeah win 7 is optimised for SSD and lucky you with an intel you hit the ground running with trim enabled so no need to worry about performance drops, may need a firmware uprade though check intel webby. Nice.
 
Nope, AFAIK new firmware has not been released yet, and if you're running on ICHxR controller Intel haven't released any updated drivers supporting TRIM yet.
 
Nope if you're running on ICHxR controller Intel haven't released any updated drivers supporting TRIM yet.

These SSDs don't seem to be "Plug and Play" like HDDs. I have a crucial 128GB - with seal intact (cautious!)

- update firmware (crucial)
- up motherboard drivers (intel)

will TRIM then work with Win 7 (only).

I may send it back and get a fast HDD!

Mel
 
If your using Windows 7 most of the hassle is going to be taken care of, it automatically disables unused things such as defrag and pre-fetching. But yea, like you say you still need to update the firmware but the process doesnt look too bad, for OCZ drives at least you can do it without damaging any data on the drive
 
These SSDs don't seem to be "Plug and Play" like HDDs. I have a crucial 128GB - with seal intact (cautious!)

- update firmware (crucial)
- up motherboard drivers (intel)

will TRIM then work with Win 7 (only).

I may send it back and get a fast HDD!

Mel


you are over complicating it

just plug it in and off you go , especially if you are using win 7
 
Windows 7 should configure itself according to if you installed Windows 7 on a solid state drive with good random read, random write and flush performance. However, on my installation, it doesn't seem to have disabled the SuperFetch service:

SuperFetch service:

SuperfetchService.png


Disk Defragmenter service:

Defragmenter.png


This is with the Windows 7 Enterprise 90-day trial installed on a Intel X25-M G2 Solid State Drive which is the only hard drive I have installed.

What is everyone else's experience regarding this?
 
Firewizard, that's correct.

It doesn't disable the services, in case you add or have any mechanical HDs, but from what I have worked out it doesn't run them on the SSD.

Try selecting your SSD when setting up a defrag schedule - it won't appear as a disk you can check against (though the check all disks is misleading). Anyway, it's easier to see if you have both SSD and mechanical HDs.
 
It doesn't disable the services, in case you add or have any mechanical HDs, but from what I have worked out it doesn't run them on the SSD.

May I ask how you came to that conclusion please?

Try selecting your SSD when setting up a defrag schedule - it won't appear as a disk you can check against (though the check all disks is misleading).

Yep, that is indeed correct.
 
Some useful info here - http://blogs.msdn.com/e7/archive/2009/05/05/support-and-q-a-for-solid-state-drives-and.aspx

Also before I got rid of mechanical drives I monitored (Winternals + Resource monitor) what was running and what was hitting the disks. Never saw Prefetch or Superfetch come into play on the SSD. Also check out C:\Windows\Prefetch it's usually full of files when Superfetch and Prefetch are running - mine has a a handful of files from date of install - but nothing since, and nothing like the number of files I'd expect on a mechanical HD.

I've only got the SSD in the box now, and Superfetch is "manual" and defrag "disabled" was "manual" but I disabled it :)
 

Yep, I read that article a while ago which is why I mentioned Windows 7 should configure itself according to if you have installed Windows 7 on a solid state drive with good random read, random write and flush performance.

You also mentioned that Windows 7 doesn't disable the services, in case you add or have any mechanical HDs, but does leave it on for solid state drives - may I ask where you found that out that piece of information please?

Also check out C:\Windows\Prefetch it's usually full of files when SuperFetch and Prefetch are running - mine has a a handful of files from date of install - but nothing since, and nothing like the number of files I'd expect on a mechanical HD.

I have done a bit of testing and the conclusion I have come too is SuperFetch, Prefetch, ReadyBoost along with ReadyBoot are still enabled in Windows 7 on a solid state drive, certainly on my installation anyway. The only settings which are disabled are Disk Defragmenter.

The following is just a short description of how Superfetch works in Windows Vista from the Inside the Windows Vista Kernel: Part 2 article by Mark Russinovich:

Mark Russinovich said:
Watching SuperFetch:

After you've used a Windows Vista system a while, you'll see a low number for the Free Physical Memory counter on Task Manager’s Performance page. That's because SuperFetch and standard Windows caching make use of all available physical memory to cache disk data. For example, when you first boot, if you immediately run Task Manager you should notice the Free Memory value decreasing as Cached Memory number rises. Or, if you run a memory-hungry program and then exit it (any of the freeware "RAM optimizers" that allocate large amounts of memory and then release the memory will work), or just copy a very large file, the Free number will rise and the Physical Memory Usage graph will drop as the system reclaims the deallocated memory. Over time, however, SuperFetch repopulates the cache with the data that was forced out of memory, so the Cached number will rise and the Free number will decline.

Superfetch.png


Watching memory(Click the image for a larger view)

I went on to simulate what Mark Russinovich said regarding running and then exiting a memory intensive program and looking at how SuperFetch reacts with the SuperFetch service on it's default settings in Windows 7 compared to disabling the service manually.

SuperFetch enabled:

This very first image is showing the SuperFetch service settings untouched after having installed Windows 7 on my solid state drive, along with Memtest running which was the program I used to quickly allocate large amounts of memory:

Superfetchenabled.png


I then exited Memtest and waited around 30 minutes before I took the image below and as you can see, SuperFetch has repopulated the cache:

Superfetchenabled-1.png


SuperFetch disabled:

I then disabled the SuperFetch service and ran Memtest again:

Superfetchdisbaled.png


I exited Memtest and waited around 40 minutes till I took the image below. Since SuperFetch has been disabled, the cache value is significantly lower:

Superfetchdisbaled-1.png


- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

SuerpeFetch / Prefetch enabled:

The second test I did was to see activity of the C:\Windows\Prefetch folder - The image below was taken after I had been using my system for a while with the SuperFetch service setting in it's default setting:

Superfetchenabled-Prefetchfolder.png


SuperFetch / Prefetch disabled:

This next image is with the SuperFetch service disabled after I had been using my system for a while. However, since SuperFetch has been disabled, there are obviously no files in the folder:

Superfetchdisabled-Prefetchfolder.png


- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

ReadyBoost:

I then went to see if ReadyBoost had been disabled after a clean installation of Windows 7 - The image below is showing the ReadyBoost feature still available to removable storages devises:

Readyboost.png


- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

ReadyBoot enabled:

The very last test I did was with regards to ReadyBoot, which also does not seem to be disabled on a default installation of Windows 7 on a solid state drive - This first image is showing ReadyBoot enabled along with it's folder in the C:\Windows\Prefetch folder:

Readybootenabled.png


ReadyBoot disabled:

I then restarted the system so I could delete the "ReadyBoot" folder. Once I had logged back on, I disabled ReadyBoot and then restarted my system to see if the "ReadyBoot" folder would be created. As confirmed by the image below, it wasn't:

Readybootdisabled.png


I've only got the SSD in the box now, and Superfetch is "manual" and defrag "disabled" was "manual" but I disabled it :)

When you first installed Windows 7 on your solid state drive, did the settings reflect my settings in my post here?
 
Hi all I just wanna test my drive before Win7 is released... so im gonna use it as a slave


What Allocation Unit Size should i specify?

Thanks in adv
 
Hi Fire Wizard - thanks for sharing your findings.

I updated the firmware on my drives yesterday and have just completed a clean install. The plot thickens...

I am now finding the exact same results you are.

I am absolutely certain that on my previous install Superfetch was set to "manual" and stopped. I double checked before responding to you. I am also absolutely certain that I had not manually altered the Superfetch service.

Defrag was also set to "manual" and stopped, but I do know that I later changed that to "disabled".

Reviewing my backup before the reinstall shows my Prefetch folder as;

prefetchold.jpg


And Readyboot as;

readybootold.jpg


02/09/2009 was the day I installed Windows 7.

Today's install shows a very different story;

prefetchnew.jpg


readybootnew.jpg


On the current install Readyboot is "enabled", I can't check the Trace for the previous install, but the dates in the readyboot folder suggest it was not running after the first install (i.e. all dates were 02/09/2009 whereas when it is enabled it seems to update the Readyboot files during boot).

You also mentioned that Windows 7 doesn't disable the services, in case you add or have any mechanical HDs, but does leave it on for solid state drives - may I ask where you found that out that piece of information please?

This is what I had assumed based on what I had observed on my previous install. As they were still set to "manual" and "stopped" but not "disabled".

Will Superfetch be disabled on SSDs?

Yes, for most systems with SSDs.

If the system disk is an SSD, and the SSD performs adequately on random reads and doesn’t have glaring performance issues with random writes or flushes, then Superfetch, boot prefetching, application launch prefetching, ReadyBoost and ReadDrive will all be disabled.

Initially, we had configured all of these features to be off on all SSDs, but we encountered sizable performance regressions on some systems. In root causing those regressions, we found that some first generation SSDs had severe enough random write and flush problems that ultimately lead to disk reads being blocked for long periods of time. With Superfetch and other prefetching re-enabled, performance on key scenarios was markedly improved.

What does MS consider "adequate" before it applies these changes? Should we be looking for these services to be "disabled"? I read that as the function on an SSD would be disabled, not the service itself?

I have been thinking as to why I am now seeing different results, the only change that I can think of is that when I first installed Win 7 on 02/09/2009 it was a new machine and I hadn't turned on SpeedStep or enhanced states. The install yesterday had them turned on. This is the only difference.

I do know that Speedstep does have an impact on my SSD performance (in benchmarks at least - I don't notice otherwise) and I am now wondering if this has caused the setup to treat my SSDs as "inadequate"?

I know you will think this is all BS. But I am now very confused as I am 100% certain I made no tweaks to Superfetch and I am seeing very different results with this latest install.

I guess the only way to validate whether Speedstep is influencing the install is to reinstall with Speedstep disabled, but I am not going to get the time to do that for a couple of weeks at least :(

Do you have any thoughts why I may be seeing this? :confused:
 
Windows 7 will recognise the SSD as an SSD if you do the installation in IDE mode (BIOS flag). If you install with AHCI/RAID mode enabled, Windows 7 defers to the Intel controller and will set the drive up like any other drive.

To work around this issue, unplug all drives but your SSD, set the BIOS to IDE and install the Operating System. Once you have installed, you will need to tell Windows to load the AHCI driver at boot:

http://www.ithinkdiff.com/how-to-enable-ahci-in-windows-7-rc-after-installation/

You can then reenable AHCI/RAID in the BIOS and power up your other disks, with the correct tweaks applied to the SSD. (or you can set them yourself, it's not complicated :))

AHCI / RAID gives you a couple of things, hot swap and access to the Intel Matrix software for managing RAID drives. You lose access to Trim until Intel updates the ICHxR drivers.

I tested this over the weekend with the 90 day eval of Windows 7 Enterprise from Technet.
 
Windows 7 will recognise the SSD as an SSD if you do the installation in IDE mode (BIOS flag). If you install with AHCI/RAID mode enabled, Windows 7 defers to the Intel controller and will set the drive up like any other drive.

To work around this issue, unplug all drives but your SSD, set the BIOS to IDE and install the Operating System. Once you have installed, you will need to tell Windows to load the AHCI driver at boot:

http://www.ithinkdiff.com/how-to-enable-ahci-in-windows-7-rc-after-installation/

You can then reenable AHCI/RAID in the BIOS and power up your other disks, with the correct tweaks applied to the SSD. (or you can set them yourself, it's not complicated :))

AHCI / RAID gives you a couple of things, hot swap and access to the Intel Matrix software for managing RAID drives. You lose access to Trim until Intel updates the ICHxR drivers.

I tested this over the weekend with the 90 day eval of Windows 7 Enterprise from Technet.

Sorry for the noob question but if I'm not using RAID now or in future, is there any point in configuring it as AHCI?
 
Sorry for the noob question but if I'm not using RAID now or in future, is there any point in configuring it as AHCI?

Not really, it's a quick registry edit to turn it on at a later point. You'll lose Hot Swap if that's important to you, it is to me.
 
Windows 7 will recognise the SSD as an SSD if you do the installation in IDE mode (BIOS flag). If you install with AHCI/RAID mode enabled, Windows 7 defers to the Intel controller and will set the drive up like any other drive.

To work around this issue, unplug all drives but your SSD, set the BIOS to IDE and install the Operating System. Once you have installed, you will need to tell Windows to load the AHCI driver at boot:

http://www.ithinkdiff.com/how-to-enable-ahci-in-windows-7-rc-after-installation/

You can then reenable AHCI/RAID in the BIOS and power up your other disks, with the correct tweaks applied to the SSD. (or you can set them yourself, it's not complicated :))

AHCI / RAID gives you a couple of things, hot swap and access to the Intel Matrix software for managing RAID drives. You lose access to Trim until Intel updates the ICHxR drivers.

I tested this over the weekend with the 90 day eval of Windows 7 Enterprise from Technet.


So if Win7 is installed on the SSD (Intel G2 in my case) under AHCI in the BIOS, the only issue is the tweaks are not automatically applied- is that correct? And provided that one is not using RAID, the default Microsoft AHCI drivers will be installed, rather than the Intel ones which do not support TRIM (yet)- even though Intel have still not got around to releasing the Firmware update so its a moot point anyway:(
Is there a consensus on the Page File on SSDs yet- ie Windows managed on the SSD, fixed size on a separate partition on the SSD, or fixed size on a seperate non SSD drive.
Sorry for all the questions
Thanks :)
 
Microsoft seem to recommend using the SSD for the paging file. I've just left mine at the default settings on my 160G Intel G2.

Slightly concerned that I installed Win7 in AHCI mode and that the allignment might not be optimal. Is there any easy way to check as I don't really want to redo the install in the near future now that I have Win7 Ultimate RTM installed?

Cheers
 
Back
Top Bottom