S
srd
I finally got the bright idea to actually watch the indexing process in
the Index Options control panel. When I avoided using my computer it would
start working for a couple minutes and then maybe stop for another few. It
seems to be oversensitive, trying to avoid interfering with the user but
then not getting its job done. (But then this contrasts with reports that
WDS can consume 100% of cpu. Maybe it is more accurate to say WDS is not
terribly intelligent about how it modulates its own priority.
Depending on how big a part of the problem this is, it might be resloved
by temporarily raising the indexer's priority. (What makes me think I know
what I'm talking about?) The indexer has a Normal priority and the other
two subnormal. I am going to take the Indexer up two notches for the night
and take the other two components up one notch to normal. No, why
equivocate--I'll take both up 2, lifting the other indexing components to
Above Average.
I'm going to challenge WDS to take 100% cpu.
the Index Options control panel. When I avoided using my computer it would
start working for a couple minutes and then maybe stop for another few. It
seems to be oversensitive, trying to avoid interfering with the user but
then not getting its job done. (But then this contrasts with reports that
WDS can consume 100% of cpu. Maybe it is more accurate to say WDS is not
terribly intelligent about how it modulates its own priority.
Depending on how big a part of the problem this is, it might be resloved
by temporarily raising the indexer's priority. (What makes me think I know
what I'm talking about?) The indexer has a Normal priority and the other
two subnormal. I am going to take the Indexer up two notches for the night
and take the other two components up one notch to normal. No, why
equivocate--I'll take both up 2, lifting the other indexing components to
Above Average.
I'm going to challenge WDS to take 100% cpu.