Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Other Technologies / Full-Text Search / June 2004

Tip: Looking for answers? Try searching our database.

[Q] cpu is full.. 100%

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
parkchangsoon - 28 Jun 2004 03:59 GMT
os : win2000
sql : sql2000 enterprise

table name : job
I created fulltext catalog
table is job column name : title

full population is every sunday am 5:00
incremental population is every 2hours from 7am to next day 3am

whenever server is running the both population, cpu is full 100%(see the
task manager )

Question : can i reduce the cpu use?

the columns are updated frequently are readcnt of job table

if i remove the readcnt column, the cpu use will reduce?

thanks...

below is the result of sp_spaceused job

name    rows          reserved     data       index_size   unused
------------------------------------------------------------
Jobs    259845      468808 KB  214264 KB 28128 KB     226416 KB

column_name   type
------------------------
title                  varchar(100)
findPrsn             tinyint
ageZn                varchar
applyRght         varchar
emplrId             varchar
seq                 int
readCnt             int
sido                 tinyint
workTyp             char
applyDcmnt     varchar
findYmd2         smalldatetime
gugun         tinyint
finishYmd     bit
ymd             smalldatetime
particular     char
position     varchar
logo         varchar
endymd     smalldatetime
jobtype1     tinyint
jobtype2     tinyint
jobtype3     tinyint
paytype     char
pay1         int
pay2         bit
suprise     tinyint
ts             timestamp
visible         bit
createdYmd smalldatetime
John Kane - 28 Jun 2004 07:22 GMT
parkchangsoon,
The limited duration high CPU usage you are seeing during your scheduled
Incremental Population is expected and normal as there is a lot of internal
work being processed that is not only CPU intensive, but memory and disk i/o
intensive, but only for specific durations. You can reduce the priority of
the MSSearch service via sp_fulltext_service 'resource_usage' <value>, where
<value> is by default set to 3, and set it to 1 (background). However, this
will have the affect of causing the Incremental Population to take much
longer time to complete.

Since you are using SQL Server 2000, I'd highly recommend that you look at
"Change Tracking" and "Updated Index in Background" (see the BOL for more
info on Change Tracking) as this will eliminate the need for your scheduled
Incremental Population and allow your FT Catalog to be updated in near
real-time as the FT-enabled column is updated. This will eliminate the high
cpu usage you are seeing during the scheduled Incremental Population.

Regards,
John

> os : win2000
> sql : sql2000 enterprise
[quoted text clipped - 53 lines]
> visible         bit
> createdYmd smalldatetime
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.