Monitoring dynamic indexing of high-usage views

Use the Show Tasks and Show Stats commands to monitor indexing of high-usage views.


To see which views are designated as high usage, use the Show Tasks server console command. Look for lines in the output similar to the following one:
View Indexer app\disc9.nsf "All Documents" 10 sec. high usage read 
To see statistics about high-usage views, use the following statistics with the Show Stat server console command:
Table 1. High-usage view statistics
Statistic Description
Database.ViewUsage.Calls Number of calls to update code that added to the cumulative update activity score for views.
Database.ViewUsage.HighUsageDisables Number of times that high usage views were disabled (no longer high usage).
Database.ViewUsage.HighUsageEnables Number of times that high usage views were enabled (made high usage).
Database.ViewUsage.HighUsageUpdateChecks Number of times dedicated high usage view threads checked whether views were stale
Database.ViewUsage.HighUsageUpdates Number of times dedicated high usage view threads updated views.
Database.ViewUsage.Skipped Number of times that updating the update activity scores for views was skipped to avoid semaphore contention.
Database.ViewUsage.HighUsageCurrent Current number of high usage views.
Update.View.<db-file-name>.<view-name>.Score Current score for a view.

where <statistic> is one of the following:

Count of specified NIF primitive update operations done by dedicating indexing for a specific high usage view. Use to verify specific actions resulting from dedicating view indexing of a view.
Note: The Domino server may show an increase in I/O activity due to the use of dedicated view indexing threads. Should this become a problem, disable the dynamic view indexing feature by setting NIF_VIEW_USAGE_ENABLED=0 or deleting the setting.