Video Screencast Help

Max simultaneous index upgrades

Created: 17 Mar 2013 • Updated: 05 Apr 2013 | 4 comments
dihrig's picture
This issue has been solved. See solution.

Is there a way to control the number of simultaneous index upgrades? For example, the customer wants to just load all their 32-bit indexes into an upgrade task, and let it run continuosly, but only processing 1 (or 2) at a time, in order to keep the load on the server minimal. The default of up to 30 overwhelms the server.

Operating Systems:

Comments 4 CommentsJump to latest comment

ZeRoC00L's picture

Yes, configure the value "Maximum concurrent indexing capacity" with a lower value:

If this response answers your concern, please mark it as a "solution"

dihrig's picture

That setting affects all index processing, not just those submitted via an upgrade task. Was hoping to only limit upgrades.

Tremaine's picture

If the default of 30 is overwhelming the server then they should consider permantly dropping the value to something sustainable (whatever number that may be through trial and error) or they should look at either increasing their RAM, CPU or both etc. as even without this in place they could potentially encounter issues in the future.

Also make sure that they have a 2.5-3xRAM pagefile configured.