up vote 1 down vote favorite
share [g+] share [fb]

I was minding my own business scripting along, hunting down some docs on a library i used for a piece of code that i dusted off. I searched for a simple thing ('ex', with quotes) in the documents directory for the libraries that come with the scripting language i use, and shortly thereafter, both of my CPU's jammed themselves to 100% and it seems that SearchIndexer is the culprit. Did my search trigger an indexing party or something?

link|improve this question
80% accept rate
I turn the damn thing off - I'm happy to wait for a moment while it scans through everything, than wait less, but be constantly slowed by it eating my disk I/O for reasons I'm not entirely sure of. – Phoshi Sep 13 '09 at 12:47
feedback

1 Answer

up vote 1 down vote accepted

Most likely, however I don't think it will be permanent.

The Vista/Windows 7 search indexer is good, but it can be very resource heavy if not run in a while.

If I open Outlook for the first time in a week, it is common for my CPU to be at 100% for a few minutes whilst indexing, the same goes for if I just extract a huge file (I mean 1000+ files) to an indexed location.

link|improve this answer
As i write this it's been running for at least 20-30 minutes, and i requently see it pop up and do stuff. – RCIX Sep 13 '09 at 12:15
Other times i mean. – RCIX Sep 13 '09 at 12:31
If this is just the first time it is being run, leave it for a few hours to fully index everything. If it does it after that, you could have a problem, but it is hard to know without seeing the script and understanding in detail what it is actually doing – William Hilsum Sep 13 '09 at 12:58
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.