R. C. White said:
Hi, Jeff.
I suspected as much, but it took me a day to respond..and I see you said
that "it is no longer churning and all is quiet ....."
Starting with Vista, many of us noticed a lot of disk activity for the
first few days, while the Search service built its Index. There were a
few other new-system housekeeping chores, too, such as building the
SuperFetch cache, which speeds up later accesses to the apps we use most
often. Most of these activities run only in the background so that they
don't interfere with what we are working on. In the first few days with
a new Win7 installation, we are keeping it pretty busy with foreground
tasks (installing apps, tweaking, etc.) so it doesn't get much
background time. I've often recommended that a new installation be left
on during lunch time or even overnight to let the background
housekeeping tasks finish. Then the disks don't churn so much after it
gets caught up.
Maybe that's what happened in your case. ;<)
RC
--
R. C. White, CPA
San Marcos, TX
(e-mail address removed)
Microsoft Windows MVP (2002-2010)
Windows Live Mail 2012 (Build 16.4.3503.0728)) in Win8 (RTM Ent Eval)
You can simulate this, by using the Indexing control panel and having
the Indexer repeat its operation.
On my laptop, with 26GB C:, the indexing operation takes about 3 hours.
Normally, the indexing operates at a reduced priority, in the sense
that if the user starts to use the computer, the indexer "backs off"
automatically. I find this annoying, so I applied the change where
the back off is disabled. If you leave it set up as default, the
"backed off" mode of operation, could spread that out to way more
than the 3 hour run. I found that too annoying.
If the indexer on my machine, feels it needs to generate the index all
over again, I walk away from the machine for the 3 hours until it
completes. By bumping up the priority as much as possible, I try to
get it over with.
I tried to disable "content" indexing, and just have it index file names.
If that attempt had worked, it would only take a couple minutes to make
a file list. But even with that setting disabled, the indexing operation
still does a content based index, which is why it takes the 3 hours. In
other words, for me, it ignores a user setting. All I really want is
a file index, not content indexing.
I can't imagine how long that would take, on any decent sized partition.
Especially if you have no effective control over it.
If you disable the indexer, then searches take forever to run. If
you enable the indexer, searches become faster, but the indexing
can be annoying.
You'll find at least three processes running in Task Manager, related
to indexing. A regular "three ring circus", a celebration of excess.
On my laptop, when it was new, indexing was turned off. I turned it on,
because I couldn't stand waiting the two minutes for a search operation
to complete. As long as I don't have to watch the disk chugging for
three hours, and can walk away, then it seems like a good option.
Paul