cisvc.exe driving cpu 100% hogging entire system

[Xross Trainer]

the cisvc.exe hogs up my cpu causing all programs to run
exceeding slow, please help.

Thanks

 

[Carey Frisch [MVP]]

Type SERVICES.MSC in the Run dialog box, find the 'Indexing Service' in your list,
right-click it, select Properties, and then in the Startup Type field select 'Disabled'.

If you are never really going to use indexing you can also uninstall it via Add/Remove
Programs under Windows Components.

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User

Be Smart! Protect your PC!
http://www.microsoft.com/security/protect/

--------------------------------------------------------------------------------------------


| the cisvc.exe hogs up my cpu causing all programs to run
| exceeding slow, please help.
|
| Thanks

 

[Xross Trainer]

Thanks for your advice, I only get to experience this
recently, what could have caused the cisvc.exe to drive
the cpu 100%? What is indexing? I am not sure if I need
it. Please advise and thank you.

-----Original Message-----
Type SERVICES.MSC in the Run dialog box, find

the 'Indexing Service' in your list,

right-click it, select Properties, and then in the

Startup Type field select 'Disabled'.

If you are never really going to use indexing you can

also uninstall it via Add/Remove

 

[Bob Dietz]

the cisvc.exe hogs up my cpu causing all programs to run
exceeding slow, please help.

Thanks

Cisvc.exe = Indexing Service (Content Indexing Service).

Most will tell you, simply turn it off.
That's good advice in many cases.

------------------------------

An alternative is to tune Indexing Service.

START > Run... > ciadv.msc
Action(menu) > All Tasks > Tune Performance
* Customize > Customize...>
Indexing: Lazy
Querying: Low Load
OK; OK

Before closing the Indexing Service management console, consider
modifying the system catalog to only include the folders you
want/need indexed.
Do not index FAT/FAT32 volumns. Indexing service scans them at
a fixed time interval.

See these pages about actually making use of the index in a search.
http://snipurl.com/4lpl
http://www.aimingtech.com/file_searching.htm

If having yesterdays stuff indexed is good enough and you leave
your machine on 24/7, then you may choose to use the following
*.reg file AT YOUR OWN RISK. I AM NOT LIABLE FOR DATA LOSS NOR
ANY DAMAGE THAT MAY RESULT!

-----<snip here>------------------------------------------------
Windows Registry Editor Version 5.00

; Comments are allowed in *.reg files. Just merge this file.
; There are 44 registry values in this *.reg file.

; The MSDN Indexing Service Reference (ISR) can be found at
; http://msdn.microsoft.com/library/en-us/indexsrv/html/ixref_6xid.asp
;
; Definitions for the 'Main Registry Entries' can be found at
; http://msdn.microsoft.com/library/en-us/indexsrv/html/ixrefreg_3nw3.asp


; "Vanilla" settings are NOT from a clean install.
; They are from a machine where Indexing Service was disabled
; shortly after a clean install. It's possible these values have
; been changed by a later software installs despite indexing
; service having been disabled.


; (t) = Items marked as suitable for testing.
; (n) = Items not found on my machine, which are found in ISR.
; (u) = Items found on my machine, but not found in ISR.


; Tune Performance: Yes | No - Is this value altered by
; START > Run... > ciadv.msc > Action > All Tasks > Tune Performance


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ContentIndex]

"CiCatalogFlags"=dword:00000000
; (t) Not yet tested with dword:00000001
;
; controls whether Indexing Service receives file-modification
; notifications from local or remote hosts.
; 0x00000000 (Enable all notifications) *** DEFAULT ***
; 0x00000001 = Disable notification processing for all remote
; universal naming convention (UNC) paths.
; Set this flag if Indexing Service is configured
; to index documents on a wide area network (WAN)
; over slow links.
; 0x00000002 = Disable notification processing for all local paths.
; Ox00000003 = 0x00000001 + 0x00000002



"DaemonResponseTimeout"=dword:00000005
; (t) Possibly test with dword:00000003
; A time-out interval (in minutes) that is used to determine whether the
; CiDaemon.exe indexing process is looping because of a corrupted file.
; Range: 1 - 120 minutes.
; Default: 5 minutes.




"DelayedFilterRetries"=dword:0000000A
; Vanilla dword:00000001
; ISR default: 240
; -------------------------
; Controls the number of times Indexing Service tries to index a document
; that has been placed in the secondary indexing queue because the first
; attempt to index it failed.
; Range: 0 - 32,000 retries. ISR Default: 240 retries




"DelayUsnReadOnLowResource"=dword:00000001
; Controls whether the USN journal, also known as the change-notification
; log, is examined under the following system conditions: low memory,
; high input/output (I/O), recent user activity, and running on
; battery power.
; Range: 0, 1. ISR Default: 1
;
; Remarks:
;
; Set the value of the DelayUsnReadOnLowResource entry to one to
; prevent the reading of the USN journal as long as any of the
; system conditions exist.
;
; Since indexing does not occur during these conditions, there's
; no point in examining the USN journal unless the journal has a
; fixed size (MaxUsnLogSize) and is about to become full.
; When this happens, the data being written to the journal wraps
; around, and a beginning block (USNLogAllocationDelta) is deleted
; to make room for more data. As a result, change notifications
; may be lost. If this seems likely, Indexing Service gives checking
; the USN journal a higher priority even if you have set this entry.
; Tune Performance: Yes


"DesiredIndexingPerf"=dword:00000003
; Not Documented but
; 1 = Lazy, 2 = Normal, 3 = Instant



"DesiredQueryingPerf"=dword:00000001
; Not Documented but
; 1 = Lazy, 2 = Normal, 3 = High Load



"FilterContents"=dword:00000001
; Determines if contents of files will be filtered?
; Poorly Documented. Test it.
; Boolean default 1 = filter both content and properties.
; Boolean 0 = filter only properties.




"FilterDelayInterval"=dword:0000003c
; Vanilla value was dword:00000005
; Determines the number of seconds to suspend filtering when the number
; of documents left to filter equals the value in the
; FilterRemainingThreshold entry.
; Range: 0 - 600 seconds
; Default: 20 seconds.
;
; Remarks:
; The FilterDelayInterval value can prevent Indexing Service from
; overusing resources while trying to index temporary files created
; by running applications. Increase the value of this entry if filtering
; certain files uses more resources than allowed.



"FilterIdleTimeout"=dword:000927C0
; 600,000 = 10 minutes
; Vanilla value was dword:000493e0
; Controls the time interval after which unused IFilter DLLs loaded
; by the CiDaemon.exe process are released.
; Range: 0–4294967295 (0xFFFFFFFF) milliseconds
; Default: 900,000 or 0x000DBBA0 (15 minutes)
; maybe this is affected by "Tuneup Performance Setting"???



"FilterRemainingThreshold"=dword:00000040
; vanilla value was dword:00000005
; Delays filtering if the number of documents to be filtered is less
; than the number of files set in the value of this registry entry.
; Range: 0-320 files.
; Default: 32 files.
;
; Remarks:
; The delay specified by the value of the FilterRemainingThreshold
; entry prevents Indexing Service from overusing resources while
; trying to index temporary files created by running applications.



"FilterRetries"=dword:00000003
; vanilla value was dword:00000002
; Determines the maximum number of times Indexing Service will try
; to filter a file after the initial filtering attempt fails.
; Range: 1 - 10 retries.
; Default: 4 retries.



"FilterRetryInterval"=dword:0000000f
; vanilla value was dword:00000005
; Determines the time interval between attempts to filter the
; contents of a file that is being used by another process.
; Range: 2 - 240 minutes.
; Default: 30 minutes.




"LowResourceCheckInterval"=dword:00000014
; if this works ok try dword:0000000A, then dword;00000005
; vanilla value was dword:0000003c
; The minimum time interval available for creating wordlists during
; the indexing process before Indexing Service checks system resources.
; Range: 5 - 4294967295 (0xFFFFFFFF) seconds.
; Default: 60 (0x0000003c) seconds.
;
; Remarks:
; After an interval specified by the value of the LowResourceCheckInterval
; entry passes, the indexing process checks system resource limitations
; such as low memory or heavy I/O initiated by the end user.



"LowResourceSleep"=dword:0000012C
; wait for 5 minutes. May increase this
; vanilla value was dword:00000005
; The time interval that Indexing Service waits after low-resource
; conditions occur before retrying the affected processing.
; Range: 5 - 1200 seconds.
; Default: 180 seconds.
;
; Remarks:
; When system resource limitations (such as low memory or heavy I/O
; initiated by the end user) occur, Indexing Service suspends processing
; for a time interval equal to the value of the LowResourceSleep entry
; before trying to resume the processing.



"MasterMergeCheckpointInterval"=dword:00002000
; The amount of information indexed before Indexing Service generates
; a checkpoint for a master merge.
; Range: 256 - 4096 Kilobytes.
; Default: 2048 (0x00002000) Kilobytes.
;
; Remarks:
; Determines how much work (data written to the new master index)
; needs to be redone if a master merge is paused and restarted.



"MasterMergeTime"=dword:0000003c
; Indicates the number of minutes after midnight
; at which a master merge will occur.
; Range: 0 - 1439 minutes.
; Default: 0 minutes after midnight.
; Default may not be documented correctly.
; Possibly Default: 60 (0x0000003c)?



"MaxAutoAliasRefresh"=dword:0000000F
; http://msdn.microsoft.com/library/en-us/indexsrv/html/ixrefreg_4sko.asp
; Not present on my system
; The frequency with which Indexing Service refreshes
; aliases for file shares.
; Range: 0 – 10080 (0x00002760) minutes (one week).
; Default: 15 minutes.



"MaxDaemonVmUse"=dword:0000A000
; Test with a smaller value?
; http://msdn.microsoft.com/library/en-us/indexsrv/html/ixrefreg_58yt.asp
; The maximum amount of page-file space allocated
; to virtual memory for a filter daemon.
; Range: 10240 - 4194303 Kilobytes
; (0x00002800 - 0x003FFFFF)
; ( 10MB to 4 GB - 1 byte)
; Default: 40960 Kilobytes
; (40 MB)
;
; Remarks:
; Attempted allocations beyond the value of the MaxDaemonVmUse
; entry will fail.
;
; Bob's comments. Results of a allocation failure will be ... what?
; My first guess: there may not be much point to tweaking this
; value, though it's probably larger than needed on a person
; computer or workstation.



"MaxFilesizeFiltered"=dword:00000100
; The maximum size of a file that the default filter
; will process for contents.
; Range: <not specified>
; Default: 256 (0x00000100) Kilobytes.
;
; Remarks:
; If the default filter is used for a file that is bigger
; than the value of the MaxFilesizeFiltered entry,
; only the file properties are filtered.
;
; Does not apply to the filtering of registered file types.



"MaxFreshCount"=dword:00004E20
; vanilla value was dword:000186a0
; The maximum number of files for which the latest indexed data
; is not in the master index.
; Range: 1000 – 4,294,967,295 files.
; (0x00002710 - 0x000xFFFFFFFF)
; Default: 20000 (0x00004E20)
;
; Remarks:
; When the value of the MaxFreshCount entry is reached,
; a master merge is started.



"MaxFreshDeletes"=dword:00002710
; The maximum number of files deleted from the master index
; before the master index is updated.
; Range: 10 – 4,294,967,295 files.
; (0x0000000A - 0x000xFFFFFFFF)
; Default: 320 files.
; (0x00000140)
;
; Remarks:
; When the value of the MaxFreshDeletes entry is reached, a merge is started.



"MaxPendingDocuments"=dword:00000020
; Proably want to bump this up to 100 - 200
; The maximum number of documents waiting to be filtered
; before the index is considered out-of-date for property queries.
; Range: 1 - 50000 documents.
; Default: 32 documents.



"MaxQueryExecutionTime"=dword:00007530
; 30,000 = 30 seconds
; vanilla value was dword:ffffffff
; The maximum amount of execution time allowed for a query.
; Range: 0 – 4294967295 milliseconds of CPU time.
; Default: 10000 milliseconds of CPU time. (10 seconds)
;
; Remarks:
; If a query takes more CPU time than specified by the value
; of the MaxQueryExecutionTime entry, processing of the query
; stops and an error status is returned. The value of zero specifies
; either that there is no limit for Indexing Service processing or
; that the client specifies the limit.



"MaxQueueChunks"=dword:00000014
; At some point try reducing this to dword:0000000A
; The maximum number of buffers in memory that can be used
; for keeping track of unfiltered documents.
; Range: 10 - 30 buffers.
; Default is 20 buffers.
;
; Remarks:
; The larger the value, the less frequently data needs to be written to disk.
; Bob's comment how big is a buffer?



"MaxRestrictionNodes"=dword:00001388
; I put this back to it's "default" value because it seemed too large.
; vanilla setting was dword:00040000
; The maximum number of query restriction nodes that can be created
; by Indexing Service in a single query
; Range: 1 – 4294967295 nodes.
; Default: 5000 nodes. (0x00001388).



"MaxShadowFreeForceMerge"=dword:000001f4
; This needs more though.
; Specifies the percentage of available disk space that can be used
; by shadow indexes on a catalog drive before a master merge is triggered.
; Range: 5 - 100 percent.
; Default: 20 percent.
;
; Remarks:
; If the percentage of disk space used by shadow indexes exceeds the value
; of the MaxShadowFreeForceMerge entry, and if the total free disk space
; falls below the minimum set in the MinDiskFreeForceMerge,
; a master merge begins.



"MaxShadowIndexSize"=dword:0000000f
; This also needs more thought.
; The maximum percentage of total disk space that can be occupied by
; shadow indexes on the catalog drive before a master merge is triggered.
; Range: 5 - 25 percent.
; Default: 15 percent.



"MaxWordlistIo"=dword:0000019A
;
; Specifies the system I/O threshold above which indexing
; (word-list creation) is delayed.
; Range: 100 – 4294967295 Kilobytes/second.
; Default: 410 Kilobytes/second (~2 MB / 5 sec.)
; Bob's comment. This and other excessive values must be due
; to an experiment with the "Instant" Indexing setting in
; Tuneup.
;
; Remarks:
; The value of the MaxWordlistIo entry provides one method
; of fine-tuning Indexing Service.
; Checking the I/O usage by the system is one of the ways
; Indexing Service limits its resource use so that it can
; remain an unobtrusive process.
;
; When the disk-performance counters are enabled in the
; DISKPERF.exe process, the value of the MaxWordlistIoDiskPerf
; entry is used instead of the value of this entry.



"MaxWordlistIoDiskPerf"=dword:0000000A
; Specifies the system I/O threshold above which indexing
; (word-list creation) is delayed when disk-performance
; counters are enabled.
; Range is 1 - 100 percent. Default is 10 percent.
;
; Remarks:
; The value of the MaxWordListIoDiskPerf entry is enabled only
; if counters in the DISKPERF.exe process are enabled.
; When the disk-performance counters are enabled, the value of this
; entry is used instead of the value of the MaxWordlistIo entry.



"MaxWordLists"=dword:0000001E
; vanilla value was dword:000003f4
; The maximum number of word lists that can exist.
; Range: 10 - 30 word lists.
; Default; 20 word lists.
;
; Bob's comment. Obviously the docs are wrong. Look
; at the value here. 1012 = 0x000003f4
; Bob says, another goofy value on my system.
;
; Exceeding the limit specified in the value of the MaxWordLists
; entry triggers a shadow merge to the master index.



"MinDiskFreeForceMerge"=dword:0000000f
; Needs more thought
; The minimum percentage of free space that must be available
; on the catalog drive to keep Indexing Service
; from beginning a master merge.
; Range: 5 - 25 percent.
; Default: 15 percent.
;
; Remarks:
; If the free space falls below the value specified by the
; MinDiskFreeForceMerge entry and the disk space occupied
; by the shadow indexes exceeds MaxShadowFreeForceMerge,
; a master merge is started.



"MinDiskSpaceToLeave"=dword:00000014
; 20 megabytes seems extreamly tight for modern multigig disks!
; The minimum amount of free disk space to leave on a disk.
; Range: 0 – 4294967295 megabytes.
; Default: 20 megabytes.
;
; Remarks:
; When the amount of free disk space falls below the value specified
; by the MinDiskSpaceToLeave entry, additional attempts to extend the
; allocation for catalog files fail.



"MinimizeWorkingSet"=dword:00000001
; Controls whether to minimize the size of the working set
; (the set of memory pages in physical RAM memory visible to a process)
; when Indexing Service is idle.
; Range: 0, 1 (Boolean)
; Default: 1 ( non-server editions of Nt, 2K, XP )
; (server editions default to 0)
;
; Remarks:
; If the value of the MinimizeWorkingSet entry is nonzero, the working
; set for Indexing Service is kept to a minimum to keep the indexing
; process unobtrusive.



"MinMergeIdleTime"=dword:0000005a
; The minimum percentage of CPU processing time that must be idle
; during a merge-check period before Indexing Service can initiate
; an annealing merge.
; Range: 10 - 100 percent.
; Default: 90 percent.
;
; Remarks:
; Indexing Service uses the value of the MinMergeIdleTime entry
; to delay merges until there are no other heavy demands on the processor.



"MinSizeMergeWordlists"=dword:000000ce
; Let shadow merges happen as necessary.
; vanilla value dword:00000400
; The minimum combined size of word lists that will force a shadow merge.
; Range: 1024 - 10240 Kilobytes.
; Default: 1024 Kilobytes.



"MinWordlistMemory"=dword:00000005
; Don't know exactly what this means. Can data be paged to disk
; to get this amount of memory? This is probably a tweakable setting.
; The minimum amount of free memory required for word-list creation.
; Range: 1 - 100 Megabytes.
; Default: 5 Megabytes.



"PropertyStoreBackupSize"=dword:00000200
; This can probably be lowered to dword:00000100
; Determines the number of system pages held on disk to back
; up the primary property cache.
; Range: 32 – 500000 pages (x86 processors),
; 16 – 250000 pages (RISC processors)
; Default: 1024 pages (x86 processors),
; 512 pages (RISC processors)
; Default for either totals about 4 Megabytes of memory.



"PropertyStoreMappedCache"=dword:00000004
; The maximum number of pages from the primary property
; cache that should be kept in memory at any one time.
; Range: 0 – 4294967295 pages.
; Default: 16 pages.
;
; Remarks:
; The SecPropertyStoreMappedCache entry serves the same function
; for the secondary property cache.
; Lazy - Lazy = 00000004



"ScanBackoff"=dword:00000003
; Test this with larger values like 6 or 7.
; Controls the relative use of system resources by Indexing Service
; when performing scans.
; Range: 0 - 20
; (11 - 20 reserved for future use).
; Default: 3
;
; Remarks:
; A value of zero for the ScanBackoff entry specifies full use of the
; allowable system resources when Indexing Service is doing a scan.
; A value of 10 specifies very conservative use of system resources
; during the scan. Values in the range 11 – 20 are reserved.



"SecPropertyStoreBackupSize"=dword:00000200
; This can probably be lowered to dword:00000100
; Determines the number of system pages held in memory to back
; up the secondary property cache.
; Range: 32 – 500000 (x86 processors),
; 16 – 250000 (RISC processors)
;
; Default: 1024 (x86 processors),
; 512 (RISC processors)
;
; Remarks:
; For details, see the PropertyStoreBackupSize entry.



"SecPropertyStoreMappedCache"=dword:00000004
; The maximum number of pages from the secondary property cache
; that are to be kept in memory at any one time.
; Range: 0 – 4294967295 pages.
; Default: 16 pages.
;
; Remarks:
; See PropertyStoreMappedCache.



"UsnReadMinSize"=dword:00002000
; The minimum size that the USN journal must attain before processing
; of change notifications can proceed.
; Range: 1 - 524,288 bytes.
; Default: 4096 bytes.
;
; Remarks:
; The processing of change notifications proceeds when either the size of
; the USN journal reaches the value of the UsnReadMinSize entry or an interval
; of time equal to the value of the UsnReadTimeout entry has passed
; (and there are entries in the USN journal).



"UsnReadTimeout"=dword:000001E0
; May be to aggressive - or not? dword:0000A8C0 ????
; vanilla value was dword:00000078
; The maximum interval of time for the indexing process to wait before
; processing change notifications in the USN journal.
; Range: 0 – 43200 seconds. (12 hours)
; Default: 300 seconds. (5 minutes)
;
; Remarks:
; The processing of change notifications proceeds when either an interval
; of time equal to the value of the UsnReadTimeout entry has passed
; (and there are entries in the USN journal) or the size of the USN journal
; reaches the value of the UsnReadMinSize entry.



"WordlistUserIdle"=dword:00000258
; If user touches keyboard or mouse, no further attempt at
; indexing for 10 minutes!
; Determines whether the filtering process is suspended
; while the keyboard or mouse is in use
; and determines when filtering will resume.
; Range: 0 - 1200 seconds.
; Default: 120 seconds.
;
; The process of filtering pauses until both input devices are idle
; for the set amount of time.
; Set the value of this entry to zero if you don't want filtering
; to stop while you are using the mouse or keyboard.

 

[Guest]

See this MS document:
http://support.microsoft.com/default.aspx?scid=kb;en-
us;833228