Silmarillion
MIS
There does not seem to be a lot about this on the forums, so I will ask.
The indexing service on my Windows 2000 server runs constantly, jumping around to as high as 20-30% processor usage (on a dual PIII 1.13 GHz). Sometimes there are two instances of cidaemon.exe running. I cannot completely disable the indexing service, as it is used to index the content for our intranet. Lately, users have been complaining about intermittent lags in the DOS accounting system when they are doing data entry. I have applied W2K SP3 lately, but the slow problem predates that (it may have gotten worse since SP3, but I don't know for sure).
The main question I have is: By default, indexing service indexes the whole C: drive (36GB in my case, and we are about to add another 18 GB). Obviously this improves search times on the server, but is there any harm in removing the C: root from the indexing service (assuming the intranet directory is still being indexed)? I did a bit of testing today, and the accounting seems to improve when I stop the indexing service (there is also a noticeable corresponding drop in CPU usage). When it is running, the drive lights on the RAID5 array are on almost solid.
I also ran a defrag today and noticed the drive is quite fragmented. Does this affect the indexing? What are other people doing out there as far as defrag? I have had Executive Software's Diskeeper recommended.
The indexing service on my Windows 2000 server runs constantly, jumping around to as high as 20-30% processor usage (on a dual PIII 1.13 GHz). Sometimes there are two instances of cidaemon.exe running. I cannot completely disable the indexing service, as it is used to index the content for our intranet. Lately, users have been complaining about intermittent lags in the DOS accounting system when they are doing data entry. I have applied W2K SP3 lately, but the slow problem predates that (it may have gotten worse since SP3, but I don't know for sure).
The main question I have is: By default, indexing service indexes the whole C: drive (36GB in my case, and we are about to add another 18 GB). Obviously this improves search times on the server, but is there any harm in removing the C: root from the indexing service (assuming the intranet directory is still being indexed)? I did a bit of testing today, and the accounting seems to improve when I stop the indexing service (there is also a noticeable corresponding drop in CPU usage). When it is running, the drive lights on the RAID5 array are on almost solid.
I also ran a defrag today and noticed the drive is quite fragmented. Does this affect the indexing? What are other people doing out there as far as defrag? I have had Executive Software's Diskeeper recommended.