[Abecedary]

I decided to see what the effects of having a 4GB ReadyBoost file on a Class 6 16GB SDHC were (understanding fully well that there may not be any noticeable effects at all). Basically, it seems to slow down the bootup and resume-from-hibernate processes by about 5-7 seconds. After login/wake, I'd normally be at the desktop within a second or two (particularly after wake). With ReadyBoost enabled, it now gets me to the desktop, but then the screen flickers white a few times. After about 5 seconds of this, it then lets me use the machine. If ReadyBoost is having any other positive effects on application launch times or anything, it's definitely negated by this delay. Off it goes.

[MoInSTL]

Can lower Recycle Bin settings too. Not a speed tweak but I lowered mine anyway.

[nollie]

How can you lower the recycle bin settings?

[Abecedary]

Originally Posted by nollie

How can you lower the recycle bin settings?

Right click on the Recycle Bin, select Properties, and adjust the size.

[cohoman]

Thank you for the excellent tutorial. It made installing Win7 on my Mini 9 trouble-free.

[BrandonLive]

Great, just what the internet needs, more guides full of bad advice.

Do not disable write caching, this has nothing to do with whether or not there is a cache on the SSD itself (and even if it did, SSDs do have caches). Turning it off is a great way to make performance considerably worse.

And don't disable indexing, especially on Windows 7. That will break lots of shell features (like Libraries) and for no benefit at all.

[MoInSTL]

Have been running Windows 7 for awhile with indexing turned off'. Nothing breaks and if it had there would be numerous reports.

Interesting that your very first post is so critical.

[BrandonLive]

Originally Posted by MoInSTL

Have been running Windows 7 for awhile with indexing turned off'. Nothing breaks and if it had there would be numerous reports.

Interesting that your very first post is so critical.

If indexing is turned off, most of the Library features cease to function. They rely on the index to provide metadata-based views, filter suggestions, etc. You'll also experience slower population of items in the shell, in WMP / media center, etc, as without the index the OS will need to crack open the file on every property request.

I'm a developer on the Windows shell team, I'm critical because users have complained to us that things stop working after they've done the "tweaks" suggested here.

[WolfKeeper]

Personally, I haven't noticed any issues, but then, I'm running it on a Mini 9: I don't need or use libraries or the Media Center.

[jhoff80]

I agree about the write caching, that should be left on.

However, I've turned off indexing myself, and I've been running Windows 7 since January or so, and I use the library feature to add my WHS box's recorded TV, music, videos, etc folders to them, and haven't had any trouble until recently. With build 7000, this worked absolutely fine, with no trouble at all.

Not to sound like a jerk about it, there's probably a hidden reason for it, but 7057 seems to have artificially introduced trouble doing the same thing. As in, now on the newer build, it gives me a message about the location being unsupported..... and then displays the location anyway. It almost sounds like it's just a restriction put in because you don't like people doing that, since it worked perfectly before, and works perfectly now other than the warning message. Like I said, I'm sure there's probably some reason, but it's not apparent, since it works fine. If you could clarify the reasoning for that, then maybe it'd help people. (And as for slow population of files, I've got 8000 songs and they came up as fast on the computer with indexing off using a wireless connection as they do on the desktop with indexing on).

But, maybe we can agree anyway on a preferred solution to keep resource use on the SSD to a minimum, since seek times are almost nonexistant on the SSD so indexing local files is relatively unnecessary. Maybe a better solution than turning off indexing completely via the Windows Search service would be to go into the indexing options, and change the locations that get indexed to not include things local to the SSD. That way you would get any unnecessary read/write on the SSD, but still are able to index network files and the like (and then you'd still have Windows Search available for things like OneNote that are dependent on it as well).