Full Text computation eats too much CPU

Hi,
we are using fulltext indexes computation on Production Server.
MSSEARCH eats between 20 % and 40% in a regular manner.
It picks up to 40% then goes down to zero but some secondes later will climb
again to 20 and up to 40%
We are using System SP sp_fulltext_catalog on a main table with 2 millions
rows
and one NVarchar(255) column on which the FT Index is based.
We are searching ways to :
(1) limit CPU took by MSSEARCH
(2) allow FT computation only during a BATCH period not involving User
Activity and Perf degradation.
Many Thanks
Jean-Marc,
The CPU usage you are seeing is normal and expected behavior for the
MSSearch service during FT Indexing and some type of FT Search processing.
Specifically, for FT Indexing during the Shadow Merge and after an
Incremental or Full Population's Master Merge.
Does your production server support more than one CPU? If so, you can also
use the following command prompt command on the server to set the MSSearch
service to one CPU:
at <current_time+1_min> /interactive taskmgr.exe
and then use sp_configure to set SQL Server to use the other CPU to avoid
the MSSearch service from affecting your normal SQL Server processing. If
your production server does not support multiple CPU's, you can use the
sp_fulltext_service 'resource_usage' <value> and set <value> to 1
(background) as the default is 3 and the max is 5. This will reduce the
performance level of the MSSearch service and therefore reduce the FT
Indexing and FT Search performance levels.
Regards,
John
"Jean-Marc PUGIN" <jmpugin@.mobileworkers.com> wrote in message
news:u#zYJ6W0EHA.2540@.TK2MSFTNGP09.phx.gbl...
> Hi,
> we are using fulltext indexes computation on Production Server.
> MSSEARCH eats between 20 % and 40% in a regular manner.
> It picks up to 40% then goes down to zero but some secondes later will
climb
> again to 20 and up to 40%
> We are using System SP sp_fulltext_catalog on a main table with 2
millions
> rows
> and one NVarchar(255) column on which the FT Index is based.
> We are searching ways to :
> (1) limit CPU took by MSSEARCH
> (2) allow FT computation only during a BATCH period not involving User
> Activity and Perf degradation.
> Many Thanks
>
>