IIS Index Server - Server Issues

Author

Server Issues

DougWallace

2004-04-07, 2:49 pm

Everyday around the same time our server gets very slow and then timeouts
requests. It generally recovers on its own but never back to the speed it
was filling request before. We have an index of XML files that is linked to
our SQL Server. When this happens it seems like Index Server is seized up?
Any ideas?

Bob Dietz

2004-04-07, 2:49 pm

DougWallace wrote:

> Everyday around the same time our server gets very slow and then timeouts
> requests. It generally recovers on its own but never back to the speed it
> was filling request before. We have an index of XML files that is linked to
> our SQL Server. When this happens it seems like Index Server is seized up?
> Any ideas?
>
>

Check the value of MasterMergeTime in the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Control\ContentIndex
registry key.

See -
http://msdn.microsoft.com/library/e...refreg_7wv9.asp

Bob

DougWallace

2004-04-07, 5:41 pm

The setting is 0
Other settings for reference that are other than default that may be of
interest are as follows. If anyone can comment on these I'd be very happy.

DelayUsnReadOnLowResource = 0 (Default = 1)
FilterDelayInterval = 0 (Default = 20)
FilterIdleTimeOut = 300000 (Default = 900000)
FilterRemainingThreshold = 0 (Default = 32)
FilterRetries = 10 (Default = 4)
FilterRetryInterval = 2 (Default = 30)
GenerateCharacterization = 0 (Default = 1)
IsapiRequestQueueSize = 24 (Default = 16)
LowResourceSleep = 5 (Default 180)
MaxActiveQueryThreads = 10 (Default = 2)
MacActiveRequestTreads = 100 (Default = 2)
MaxCharacterization = 320 (Default = 160)
MaxFreshCount = 30000 (Default = 20000)
MaxFreshDeletes = 10000 (Default = 320)
MaxPendingDocuments = 1 (Default = 32)
MaxQueryExecutionTime = 30000 (Default = 10000)
MaxRestrictionNodes = 16384 (Default = 5000)
MaxShadowFreeForceMerge = 500 (Default = 20)
MaxSimultaneousRequests = 500 (Default 100)
MaxWordListIo = 4294967295 (Default = 410)
MaxWordListIoDiskPerf = 100 (Default = 10)
MaxWordLists = 25 (Default = 20)
MinIdleQueryThreads = 2 (Default = 1)
MinIdleRequestThreads = 2 (Default = 1)
MinSizeMergeWordlists = 306 (Default = 1024)
MinWordlistBattery = 0 (Default = 100)
PropertyStoreBackUpSize = 2048 (Default =1024) IT IS A TWO XEON PROCESSOR
SYSTEM
PropertyStoreMappedCache = 32 (Default = 16)
ScanBackoff = 0 (Default = 3)
SecPropertyStoreMappedCache = 32 (default 16)
ThreadClassFilter = 128 (Default = 0x40)
ThreadPriorityMerge = 4294967294 (Default = -2)
UsnReadMinSize = 1 (default = 4096)
UsnReadTimeout = 0 (Default = 300)
WordlistUserIdle = 0 (Default = 120)

"Bob Dietz" <rbdietz_1999@yahoo.com> wrote in message
news:uueir%23MHEHA.2308@tk2msftngp13.phx.gbl...
> DougWallace wrote:
>
timeouts[color=darkred]
it[color=darkred]
to[color=darkred]
up?[color=darkred]
>
> Check the value of MasterMergeTime in the
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Control\ContentIndex
> registry key.
>
> See -
> http://msdn.microsoft.com/library/e...refreg_7wv9.asp
>
> Bob

Bob Dietz

2004-04-07, 6:38 pm

Not and expert, but I'd try changing these values one at a time to see
what happens.

MaxFreshCount (increase from 30,000 to 40,000)
A master merge is trigger when this number of files have been indexed
but are not yet in the master index.

MaxFreshDeletes 10,000 > 12,500
When this number of files are deleted from the master index, the master
index is "updated".

MaxShadowFreeForceMerge = 500 (Default = 20)
According to MSDN Indexing Service Reference -
> 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.
If MinDiskFreeForceMerge is the default 15% and you have more than 15%
free space remaining on the disk(s?) you're indexing, then these values
probably aren't related to the problem. But who the heck knows how 500%
is going to be interpreted by indexing service?

UsnReadTimeout = 0 (Default = 300)
Boundary conditions like this always make me nervous. As a desperation
shot you might try setting this to 1 which will delay indexing for
updated files by a whole second.

ScanBackoff = 0 (Default = 3)
If all else fails, you might set this to 1 shortly before the expected
onset of the problem. Is there less of an impact upon queries?

ThreadPriorityMerge = 4294967294 (Default = -2)
Don't believe this is at all related to the problem, but FWIW you're
already using the default value. (unsigned 4294967294 is signed -2)

Bob

DougWallace wrote:

> The setting is 0 Other settings for reference that are other than
> default that may be of interest are as follows. If anyone can comment
> on these I'd be very happy.
>
> DelayUsnReadOnLowResource = 0 (Default = 1) FilterDelayInterval = 0
> (Default = 20) FilterIdleTimeOut = 300000 (Default = 900000)
> FilterRemainingThreshold = 0 (Default = 32) FilterRetries = 10
> (Default = 4) FilterRetryInterval = 2 (Default = 30)
> GenerateCharacterization = 0 (Default = 1) IsapiRequestQueueSize = 24
> (Default = 16) LowResourceSleep = 5 (Default 180)
> MaxActiveQueryThreads = 10 (Default = 2) MacActiveRequestTreads = 100
> (Default = 2) MaxCharacterization = 320 (Default = 160) MaxFreshCount
> = 30000 (Default = 20000) MaxFreshDeletes = 10000 (Default = 320)
> MaxPendingDocuments = 1 (Default = 32) MaxQueryExecutionTime = 30000
> (Default = 10000) MaxRestrictionNodes = 16384 (Default = 5000)
> MaxShadowFreeForceMerge = 500 (Default = 20) MaxSimultaneousRequests
> = 500 (Default 100) MaxWordListIo = 4294967295 (Default = 410)
> MaxWordListIoDiskPerf = 100 (Default = 10) MaxWordLists = 25 (Default
> = 20) MinIdleQueryThreads = 2 (Default = 1) MinIdleRequestThreads = 2
> (Default = 1) MinSizeMergeWordlists = 306 (Default = 1024)
> MinWordlistBattery = 0 (Default = 100) PropertyStoreBackUpSize = 2048
> (Default =1024) IT IS A TWO XEON PROCESSOR SYSTEM
> PropertyStoreMappedCache = 32 (Default = 16) ScanBackoff = 0 (Default
> = 3) SecPropertyStoreMappedCache = 32 (default 16) ThreadClassFilter
> = 128 (Default = 0x40) ThreadPriorityMerge = 4294967294 (Default =
> -2) UsnReadMinSize = 1 (default = 4096) UsnReadTimeout = 0 (Default =
> 300) WordlistUserIdle = 0 (Default = 120)
>
>
> "Bob Dietz" <rbdietz_1999@yahoo.com> wrote in message
> news:uueir%23MHEHA.2308@tk2msftngp13.phx.gbl...
>
>
> timeouts
>
>
> it
>
>
> to
>
>
> up?
>
>
>
>

George Cheng [MSFT]

2004-04-11, 3:37 pm

The following are the reg keys to be changed to speed up indexing. Sorry
about the formatting.

Key Data Type Recommended Setting Comments
ScanBackoff REG_DWORD 0 This key controls the length of time IS
periodically pauses while scanning a disk looking for new files. It's
useful to configure how aggressively IS should use system resources to
complete a scan. A value of 0 tells IS to not pause at all. This is
especially useful on multi-processor machines.
MaxFreshCount REG_DWORD 100,000 This controls how many documents have to
change before a master merge is started. When a catalog grows beyond a few
hundred thousand documents indexing time is dominated by master merges
rather than actual indexing. Setting this key to a large value like 100,000
decreases the frequency of master merges. Depending on the catalog, values
as high as 400,000 may substantially improve index build time.
FilterTrackers REG_MULTISZ "" Filter trackers are a way for an application
to hook into the indexing pipeline. As a document is indexed all filter
trackers listed in this key will be invoked so they can do whatever
additional processing required. By default in Windows 2000 one filter
tracker is installed that generates thumbnails of documents that are
displayed in the file explorer. It's non-trivial to generate the
thumbnails, so if you don't require them, delete the value of this key. The
value is empty by default on Windows XP.
MaxWordlistIO REG_DWORD 0xffffffff When system IO exceeds this value
indexing is temporarily paused. With the recommended value IS won't pause
regardless of system IO.
MaxWordlistIODiskPerf REG_DWORD 100 This
is another metric used for system
IO. Setting the value to 100 means indexing will never stop due to high
system IO.
MinimizeWorkingSet REG_DWORD 0 At regular intervals IS will attempt to
flush its memory usage to make room for other applications. When this value
is set to 0 the behavior is disabled.
MaxWordlistUserIdle REG_DWORD 0 When someone is actively using the keyboard
or mouse on a machine IS will by default pause indexing until the machine
is again idle. Setting this value to 0 disables this behavior.
FilterIdleTimeout
REG_DWORD 2 Setting this is useful if you are using an IFilter DLL that is
buggy or prone to hanging. When the filter daemon (cidaemon.exe) has been
idle for this long it is terminated and restarted. The default is 15
minutes, and the recommended value is 2 minutes for the impatient.
MaxIndexes
REG_DWORD 100 This controls how many indexes are created as documents are
being filtered. When an index is first being created, a large value like
100 is optimal. Once an index is initially built, queries will run faster
with a smaller value, like 25. You should change this value after the
initial index build is complete.
MaxWordlists REG_DWORD 50 This controls how many in-memory indexes are
built before they are merged and written to a shadow index on disk. The
higher the value, the faster the indexing. A setting of 50 means lots of
documents will be indexed before they are merged.
MinSizeMergeWordlists REG_DWORD 1024 Thi
s limits how much RAM in 4k pages
is used by wordlists before they are merged and written to a shadow index
on disk. More is better at the cost of RAM.

Each of these keys can be set in two places in the registry. The first
location, hklm\System\CurrentControlSet\Control\Co
ntentIndex, sets the
default for all catalogs. You can override these values for each catalog at
the subkey Catalogs\CATALOGNAME. After a default installation, some values
may not exist and may need to be added.

The default values of these keys vary depending on the product installed
(Windows 2000 Professional vs. Windows 2000 Server) and the RAM and CPUs
available at the time of installation. Some of the values change when you
tune performance in the Indexing Service MMC administration tool. The
recommended values enable better performance than can be achieved via the
MMC tool.
Once an index is up to date, a different set of registry changes can be
used to help keep the index current as changes are made to the files being
indexed. These registry keys include:

Key Data Type Recommended Setting Comments
FilterDelayInterval REG_DWORD 3 When fewer than FilterRemainingThreshold
documents remain to be filtered, Indexing Service waits for the filter
delay interval before indexing them. This is done to minimize collisions
with other applications that repeatedly write to files. If your
applications don't have this behavior (for example you use xcopy to get
files to your system instead of Microsoft Word) you can safely make this
value three seconds.
FilterRemainingThreshold REG_DWORD 5 This is the number of documents that
remain to be filtered below which FilterDelayInterval is honored.
FilterRetries REG_DWORD 2 This is the number of times Indexing Service
will retry a failed document. Don't set this to 1. Due to a bug the true
value for this is the value you set minus one. 2 tells IS to retry
documents only once.
FilterRetryInterval. REG_DWORD 2 This is the minutes Indexing Service
waits between attempts a delayed retry (as opposed to a normal retry) to a
document that failed.
DelayedFilterRetries REG_DWORD 1 This is the number of delayed retries for
failed documents. The value indicates that delayed documents will only be
retried once.
USNReadMinSize REG_DWORD 0 This tells IS to pick up all changes from the
USN Journal as soon as they occur, so changes to the disk are picked up as
soon as possible.

Thank You

George Cheng

Microsoft Application Center & Index Server Support

Note: This article has no warranties implicit or explicit.
All the content is given on the "as is" basis and the user
takes full responsibility for its use and assumption.
Microsoft Corporation Copyright 2004
All Rights Reserved

--------------------
| Date: Wed, 07 Apr 2004 17:31:25 -0500
| From: Bob Dietz <rbdietz_1999@yahoo.com>
| User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6)
Gecko/20040113
| X-Accept-Language: en-us, en
| MIME-Version: 1.0
| Subject: Re: Server Issues
| References: <uPmg7nMHEHA.128@tk2msftngp13.phx.gbl>
<uueir#MHEHA.2308@tk2msftngp13.phx.gbl>
<#$chwHOHEHA.3564@TK2MSFTNGP09.phx.gbl>
| In-Reply-To: <#$chwHOHEHA.3564@TK2MSFTNGP09.phx.gbl>
| Content-Type: text/plain; charset=us-ascii; format=flowed
| Content-Transfer-Encoding: 7bit
| Message-ID: <OaxaNAPHEHA.2164@TK2MSFTNGP12.phx.gbl>
| Newsgroups: microsoft.public.inetserver.indexserver
| NNTP-Posting-Host: host-96-82-230-24.midco.net 24.230.82.96
| Lines: 1
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.inetserver.indexserver:28228
| X-Tomcat-NG: microsoft.public.inetserver.indexserver
|
| Not and expert, but I'd try changing these values one at a time to see
| what happens.
|
| MaxFreshCount (increase from 30,000 to 40,000)
| A master merge is trigger when this number of files have been indexed
| but are not yet in the master index.
|
| MaxFreshDeletes 10,000 > 12,500
| When this number of files are deleted from the master index, the master
| index is "updated".
|
| MaxShadowFreeForceMerge = 500 (Default = 20)
| According to MSDN Indexing Service Reference -
| > 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.
| If MinDiskFreeForceMerge is the default 15% and you have more than 15%
| free space remaining on the disk(s?) you're indexing, then these values
| probably aren't related to the problem. But who the heck knows how 500%
| is going to be interpreted by indexing service?
|
| UsnReadTimeout = 0 (Default = 300)
| Boundary conditions like this always make me nervous. As a desperation
| shot you might try setting this to 1 which will delay indexing for
| updated files by a whole second.
|
| ScanBackoff = 0 (Default = 3)
| If all else fails, you might set this to 1 shortly before the expected
| onset of the problem. Is there less of an impact upon queries?
|
|
| ThreadPriorityMerge = 4294967294 (Default = -2)
| Don't believe this is at all related to the problem, but FWIW you're
| already using the default value. (unsigned 4294967294 is signed -2)
|
| Bob
|
| DougWallace wrote:
|
| > The setting is 0 Other settings for reference that are other than
| > default that may be of interest are as follows. If anyone can comment
| > on these I'd be very happy.
| >
| > DelayUsnReadOnLowResource = 0 (Default = 1) FilterDelayInterval = 0
| > (Default = 20) FilterIdleTimeOut = 300000 (Default = 900000)
| > FilterRemainingThreshold = 0 (Default = 32) FilterRetries = 10
| > (Default = 4) FilterRetryInterval = 2 (Default = 30)
| > GenerateCharacterization = 0 (Default = 1) IsapiRequestQueueSize = 24
| > (Default = 16) LowResourceSleep = 5 (Default 180)
| > MaxActiveQueryThreads = 10 (Default = 2) MacActiveRequestTreads = 100
| > (Default = 2) MaxCharacterization = 320 (Default = 160) MaxFreshCount
| > = 30000 (Default = 20000) MaxFreshDeletes = 10000 (Default = 320)
| > MaxPendingDocuments = 1 (Default = 32) MaxQueryExecutionTime = 30000
| > (Default = 10000) MaxRestrictionNodes = 16384 (Default = 5000)
| > MaxShadowFreeForceMerge = 500 (Default = 20) MaxSimultaneousRequests
| > = 500 (Default 100) MaxWordListIo = 4294967295 (Default = 410)
| > MaxWordListIoDiskPerf = 100 (Default = 10) MaxWordLists = 25 (Default
| > = 20) MinIdleQueryThreads = 2 (Default = 1) MinIdleRequestThreads = 2
| > (Default = 1) MinSizeMergeWordlists = 306 (Default = 1024)
| > MinWordlistBattery = 0 (Default = 100) PropertyStoreBackUpSize = 2048
| > (Default =1024) IT IS A TWO XEON PROCESSOR SYSTEM
| > PropertyStoreMappedCache = 32 (Default = 16) ScanBackoff = 0 (Default
| > = 3) SecPropertyStoreMappedCache = 32 (default 16) ThreadClassFilter
| > = 128 (Default = 0x40) ThreadPriorityMerge = 4294967294 (Default =
| > -2) UsnReadMinSize = 1 (default = 4096) UsnReadTimeout = 0 (Default =
| > 300) WordlistUserIdle = 0 (Default = 120)
| >
| >
| > "Bob Dietz" <rbdietz_1999@yahoo.com> wrote in message
| > news:uueir%23MHEHA.2308@tk2msftngp13.phx.gbl...
| >
| >> DougWallace wrote:
| >>
| >>
| >>> Everyday around the same time our server gets very slow and then
| >
| > timeouts
| >
| >>> requests. It generally recovers on its own but never back to the
| >>> speed
| >
| > it
| >
| >>> was filling request before. We have an index of XML files that is
| >>> linked
| >
| > to
| >
| >>> our SQL Server. When this happens it seems like Index Server is
| >>> seized
| >
| > up?
| >
| >>> Any ideas?
| >>>
| >>>
| >>
| >> Check the value of MasterMergeTime in the
| >> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Control\ContentIndex
| >> registry key.
| >>
| >> See -
| >> http://msdn.microsoft.com/library/e...refreg_7wv9.asp
| >>
| >>
| >> Bob
| >
| >
| >
|

Bob Dietz

2004-04-11, 3:37 pm

Thanks, George. I found your post quite valuale. If you have no
objection, I'll post a version with better formating.

Regards,

Bob Dietz

George Cheng [MSFT] wrote:

> The following are the reg keys to be changed to speed up indexing. Sorry
> about the formatting.
>
> Key Data Type Recommended Setting Comments
> ScanBackoff REG_DWORD 0 This key controls the length of time IS
> periodically pauses while scanning a disk looking for new files. It's
> useful to configure how aggressively IS should use system resources to
> complete a scan. A value of 0 tells IS to not pause at all. This is
> especially useful on multi-processor machines.
> MaxFreshCount REG_DWORD 100,000 This controls how many documents have to
> change before a master merge is started. When a catalog grows beyond a few
> hundred thousand documents indexing time is dominated by master merges
> rather than actual indexing. Setting this key to a large value like 100,000
> decreases the frequency of master merges. Depending on the catalog, values
> as high as 400,000 may substantially improve index build time.
> FilterTrackers REG_MULTISZ "" Filter trackers are a way for an application
> to hook into the indexing pipeline. As a document is indexed all filter
> trackers listed in this key will be invoked so they can do whatever
> additional processing required. By default in Windows 2000 one filter
> tracker is installed that generates thumbnails of documents that are
> displayed in the file explorer. It's non-trivial to generate the
> thumbnails, so if you don't require them, delete the value of this key. The
> value is empty by default on Windows XP.
> MaxWordlistIO REG_DWORD 0xffffffff When system IO exceeds this value
> indexing is temporarily paused. With the recommended value IS won't pause
> regardless of system IO.
> MaxWordlistIODiskPerf REG_DWORD 100 This
is another metric used for system
> IO. Setting the value to 100 means indexing will never stop due to high
> system IO.
> MinimizeWorkingSet REG_DWORD 0 At regular intervals IS will attempt to
> flush its memory usage to make room for other applications. When this value
> is set to 0 the behavior is disabled.
> MaxWordlistUserIdle REG_DWORD 0 When someone is actively using the keyboard
> or mouse on a machine IS will by default pause indexing until the machine
> is again idle. Setting this value to 0 disables this behavior.
> FilterIdleTimeout
> REG_DWORD 2 Setting this is useful if you are using an IFilter DLL that is
> buggy or prone to hanging. When the filter daemon (cidaemon.exe) has been
> idle for this long it is terminated and restarted. The default is 15
> minutes, and the recommended value is 2 minutes for the impatient.
> MaxIndexes
> REG_DWORD 100 This controls how many indexes are created as documents are
> being filtered. When an index is first being created, a large value like
> 100 is optimal. Once an index is initially built, queries will run faster
> with a smaller value, like 25. You should change this value after the
> initial index build is complete.
> MaxWordlists REG_DWORD 50 This controls how many in-memory indexes are
> built before they are merged and written to a shadow index on disk. The
> higher the value, the faster the indexing. A setting of 50 means lots of
> documents will be indexed before they are merged.
> MinSizeMergeWordlists REG_DWORD 1024 Thi
s limits how much RAM in 4k pages
> is used by wordlists before they are merged and written to a shadow index
> on disk. More is better at the cost of RAM.
>
> Each of these keys can be set in two places in the registry. The first
> location, hklm\System\CurrentControlSet\Control\Co
ntentIndex, sets the
> default for all catalogs. You can override these values for each catalog at
> the subkey Catalogs\CATALOGNAME. After a default installation, some values
> may not exist and may need to be added.
>
> The default values of these keys vary depending on the product installed
> (Windows 2000 Professional vs. Windows 2000 Server) and the RAM and CPUs
> available at the time of installation. Some of the values change when you
> tune performance in the Indexing Service MMC administration tool. The
> recommended values enable better performance than can be achieved via the
> MMC tool.
> Once an index is up to date, a different set of registry changes can be
> used to help keep the index current as changes are made to the files being
> indexed. These registry keys include:
>
> Key Data Type Recommended Setting Comments
> FilterDelayInterval REG_DWORD 3 When fewer than FilterRemainingThreshold
> documents remain to be filtered, Indexing Service waits for the filter
> delay interval before indexing them. This is done to minimize collisions
> with other applications that repeatedly write to files. If your
> applications don't have this behavior (for example you use xcopy to get
> files to your system instead of Microsoft Word) you can safely make this
> value three seconds.
> FilterRemainingThreshold REG_DWORD 5 This is the number of documents that
> remain to be filtered below which FilterDelayInterval is honored.
> FilterRetries REG_DWORD 2 This is the number of times Indexing Service
> will retry a failed document. Don't set this to 1. Due to a bug the true
> value for this is the value you set minus one. 2 tells IS to retry
> documents only once.
> FilterRetryInterval. REG_DWORD 2 This is the minutes Indexing Service
> waits between attempts a delayed retry (as opposed to a normal retry) to a
> document that failed.
> DelayedFilterRetries REG_DWORD 1 This is the number of delayed retries for
> failed documents. The value indicates that delayed documents will only be
> retried once.
> USNReadMinSize REG_DWORD 0 This tells IS to pick up all changes from the
> USN Journal as soon as they occur, so changes to the disk are picked up as
> soon as possible.
>
>
>
> Thank You
>
> George Cheng
>
> Microsoft Application Center & Index Server Support
>
> Note: This article has no warranties implicit or explicit.
> All the content is given on the "as is" basis and the user
> takes full responsibility for its use and assumption.
> Microsoft Corporation Copyright 2004
> All Rights Reserved
>
> --------------------
> | Date: Wed, 07 Apr 2004 17:31:25 -0500
> | From: Bob Dietz <rbdietz_1999@yahoo.com>
> | User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6)
> Gecko/20040113
> | X-Accept-Language: en-us, en
> | MIME-Version: 1.0
> | Subject: Re: Server Issues
> | References: <uPmg7nMHEHA.128@tk2msftngp13.phx.gbl>
> <uueir#MHEHA.2308@tk2msftngp13.phx.gbl>
> <#$chwHOHEHA.3564@TK2MSFTNGP09.phx.gbl>
> | In-Reply-To: <#$chwHOHEHA.3564@TK2MSFTNGP09.phx.gbl>
> | Content-Type: text/plain; charset=us-ascii; format=flowed
> | Content-Transfer-Encoding: 7bit
> | Message-ID: <OaxaNAPHEHA.2164@TK2MSFTNGP12.phx.gbl>
> | Newsgroups: microsoft.public.inetserver.indexserver
> | NNTP-Posting-Host: host-96-82-230-24.midco.net 24.230.82.96
> | Lines: 1
> | Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
> | Xref: cpmsftngxa06.phx.gbl microsoft.public.inetserver.indexserver:28228
> | X-Tomcat-NG: microsoft.public.inetserver.indexserver
> |
> | Not and expert, but I'd try changing these values one at a time to see
> | what happens.
> |
> | MaxFreshCount (increase from 30,000 to 40,000)
> | A master merge is trigger when this number of files have been indexed
> | but are not yet in the master index.
> |
> | MaxFreshDeletes 10,000 > 12,500
> | When this number of files are deleted from the master index, the master
> | index is "updated".
> |
> | MaxShadowFreeForceMerge = 500 (Default = 20)
> | According to MSDN Indexing Service Reference -
> | > 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.
> | If MinDiskFreeForceMerge is the default 15% and you have more than 15%
> | free space remaining on the disk(s?) you're indexing, then these values
> | probably aren't related to the problem. But who the heck knows how 500%
> | is going to be interpreted by indexing service?
> |
> | UsnReadTimeout = 0 (Default = 300)
> | Boundary conditions like this always make me nervous. As a desperation
> | shot you might try setting this to 1 which will delay indexing for
> | updated files by a whole second.
> |
> | ScanBackoff = 0 (Default = 3)
> | If all else fails, you might set this to 1 shortly before the expected
> | onset of the problem. Is there less of an impact upon queries?
> |
> |
> | ThreadPriorityMerge = 4294967294 (Default = -2)
> | Don't believe this is at all related to the problem, but FWIW you're
> | already using the default value. (unsigned 4294967294 is signed -2)
> |
> | Bob
> |
> | DougWallace wrote:
> |
> | > The setting is 0 Other settings for reference that are other than
> | > default that may be of interest are as follows. If anyone can comment
> | > on these I'd be very happy.
> | >
> | > DelayUsnReadOnLowResource = 0 (Default = 1) FilterDelayInterval = 0
> | > (Default = 20) FilterIdleTimeOut = 300000 (Default = 900000)
> | > FilterRemainingThreshold = 0 (Default = 32) FilterRetries = 10
> | > (Default = 4) FilterRetryInterval = 2 (Default = 30)
> | > GenerateCharacterization = 0 (Default = 1) IsapiRequestQueueSize = 24
> | > (Default = 16) LowResourceSleep = 5 (Default 180)
> | > MaxActiveQueryThreads = 10 (Default = 2) MacActiveRequestTreads = 100
> | > (Default = 2) MaxCharacterization = 320 (Default = 160) MaxFreshCount
> | > = 30000 (Default = 20000) MaxFreshDeletes = 10000 (Default = 320)
> | > MaxPendingDocuments = 1 (Default = 32) MaxQueryExecutionTime = 30000
> | > (Default = 10000) MaxRestrictionNodes = 16384 (Default = 5000)
> | > MaxShadowFreeForceMerge = 500 (Default = 20) MaxSimultaneousRequests
> | > = 500 (Default 100) MaxWordListIo = 4294967295 (Default = 410)
> | > MaxWordListIoDiskPerf = 100 (Default = 10) MaxWordLists = 25 (Default
> | > = 20) MinIdleQueryThreads = 2 (Default = 1) MinIdleRequestThreads = 2
> | > (Default = 1) MinSizeMergeWordlists = 306 (Default = 1024)
> | > MinWordlistBattery = 0 (Default = 100) PropertyStoreBackUpSize = 2048
> | > (Default =1024) IT IS A TWO XEON PROCESSOR SYSTEM
> | > PropertyStoreMappedCache = 32 (Default = 16) ScanBackoff = 0 (Default
> | > = 3) SecPropertyStoreMappedCache = 32 (default 16) ThreadClassFilter
> | > = 128 (Default = 0x40) ThreadPriorityMerge = 4294967294 (Default =
> | > -2) UsnReadMinSize = 1 (default = 4096) UsnReadTimeout = 0 (Default =
> | > 300) WordlistUserIdle = 0 (Default = 120)
> | >
> | >
> | > "Bob Dietz" <rbdietz_1999@yahoo.com> wrote in message
> | > news:uueir%23MHEHA.2308@tk2msftngp13.phx.gbl...
> | >
> | >> DougWallace wrote:
> | >>
> | >>
> | >>> Everyday around the same time our server gets very slow and then
> | >
> | > timeouts
> | >
> | >>> requests. It generally recovers on its own but never back to the
> | >>> speed
> | >
> | > it
> | >
> | >>> was filling request before. We have an index of XML files that is
> | >>> linked
> | >
> | > to
> | >
> | >>> our SQL Server. When this happens it seems like Index Server is
> | >>> seized
> | >
> | > up?
> | >
> | >>> Any ideas?
> | >>>
> | >>>
> | >>
> | >> Check the value of MasterMergeTime in the
> | >> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Control\ContentIndex
> | >> registry key.
> | >>
> | >> See -
> | >> http://msdn.microsoft.com/library/e...refreg_7wv9.asp
> | >>
> | >>
> | >> Bob
> | >
> | >
> | >
> |
>