Indexing Service = CPU Usage 100%

[lopri]

I'm on WinXP Pro, and recently installed IIS. In order to run IIS, I started the indexing service through services.msc and set its property at "auto." so I don't have to start it mannually everytime I reboot the system. After a short while, I noticed a strange lag on my system. First I thought it's my portable USB hard drive that caused the lagginess, but after I detached the portable HD, I still had this random lag problem. I looked in the Task Manager and there was no application running but the CPU usage was at 100% (!). So I was like WTH??? I clcked on the next tap to see if there was any process eating system resource. While there was no huge memory usage but the indexing service (cisvc.exe) and a few other services (presumably related to the indexing service) was using 100% of CPU!! Holy ..!

I stopped the indexing service and now everything is back to normal and I see the CPU usage bar is down to under 5% when idle, but I need to use the indexing service somehow for my web server to run using IIS. I know it's not a server version of Windows but it's still very usefull for practicing purposes. Can anyone help me out? Thanks!

Lopri

 

[lopri]

Oh and btw, the CPU is P4 2.26GHz, and have 512 MB of RDRAM.

 

[lopri]

Anyone?

 

[Bananas4me]

Check this out...forum.

 

[bsobel]

but I need to use the indexing service somehow for my web server to run using IIS.

I don't understand this comment. Are you using some index server functionality you want on your IIS server? If not, IIS does not require index server.

Bill

 

[NogginBoink]

This makes sense. When indexing is first turned on, it'll have to scan all the files and build the index. As long as the priority of this process is set to low, and other process that has work to do will interrupt the indexing and indexing will only take place when the machine would otherwise be idle.