3 ms·

Windows 7 STILL does this in fact. I am currently using Windows 7 in my personal machine (and Linux in others). The indexing service often gets disabled becau

Windows 7 STILL does this in fact. I am currently using Windows 7 in my personal machine (and Linux in others). The indexing service often gets disabled because it makes the machine slow down a lot. Also I really miss Linux "swapyness", Windows Vista+ (10 included) are really aggressive in swapping, more than needed, often my machine ended trashing because of Swap while still having 20+ GB free, this is in part because of that stupid indexing and cache, Windows 7 has a habit of giving priority to the cache, putting files from the most accessed programs in the RAM, and not caring if your CURRENT program need RAM...

sumtechguy 6y ago
I use the indexer setup to ignore parts of my system. That works pretty good. Especially if you are doing any work with nodejs. Also defragging just the index file helps a lot. That thing can end up with thousands of bits all over the drive. Even with SSD it is not great as random seek on many SSDs are fairly terrible and contig read is amazing. One trick I also do is pre-allocate my swap file (I usually pin it to 4GB). As the default is to grow/shrink.. That can do the same thing as the indexing file. Something also changed around sp2 with 7 and file writes. Files get fragmented very quickly now even when there is plenty of space not to do so. I usually would only end up with systems badly fragmented in XP if the drive is full (much like ext4) now it just does it as a matter of course and is acting like the old DOS alg of find the next free spot. You can still turn off the readyboost/superfetch cache service (not sure where it is win10). If you have an SSD you should not notice much difference on or off but it can happen. Turning those off makes your free RAM act more like in linux where it just caches recently read items and gives it up right away if needed.

sumtechguy 6y ago

I use the indexer setup to ignore parts of my system. That works pretty good. Especially if you are doing any work with nodejs. Also defragging just the index file helps a lot. That thing can end up with thousands of bits all over the drive. Even with SSD it is not great as random seek on many SSDs are fairly terrible and contig read is amazing. One trick I also do is pre-allocate my swap file (I usually pin it to 4GB). As the default is to grow/shrink.. That can do the same thing as the indexing file. Something also changed around sp2 with 7 and file writes. Files get fragmented very quickly now even when there is plenty of space not to do so. I usually would only end up with systems badly fragmented in XP if the drive is full (much like ext4) now it just does it as a matter of course and is acting like the old DOS alg of find the next free spot. You can still turn off the readyboost/superfetch cache service (not sure where it is win10). If you have an SSD you should not notice much difference on or off but it can happen. Turning those off makes your free RAM act more like in linux where it just caches recently read items and gives it up right away if needed.