LDD Today


[back to "Optimizing server performance: Semaphores (Part 2)"]

How we used output from Show DBS (sidebar)
We converted a subset of the output from the Show DBS command from one of our R5 Domino servers into a table. Some of the columns of information helped detect bottleneck situations and helped us make optimization decisions before we made the final R5 release. So to understand the output in greater detail, understand that the database entries listed reflect which databases are requested for access; this list is not a superset or a subset of the entries in the Database Cache (see the output from the Show Directory command for the Database Cache entry list).

Name
Refs
Mod
FDs
LockWaits
Avg Waits
#Waiters
MaxWaiters
mail\cnoyes.nsf
3
N
1
0
0
0
0
Alice!!mail\hankins.nsf
2
N
0
0
0
0
0
mail\bhankins.nsf
4
Y
3
0
0
0
2
mail\rstephen.nsf
3
N
1
0
0
0
0
kerry\50Status.nsf
3
N
1
0
0
0
1
mail\mvincenz.nsf
3
N
1
0
0
0
0
StrHockey.nsf
3
Y
1
0
0
0
0
mail\rmaffa.nsf
7
N
1
0
0
0
1
clubusy.nsf
1
N
1
0
0
0
5
lotnames.nsf
73
N
20
0
0
0
4
notnames.nsf
79
N
17
0
0
0
1
names.nsf
128
N
17
0
0
0
3

Based on the table above, read the following way we used output from the Show DBS command to help detect semaphore issues:

For a practical observation, we used Show DBS output as part of our development efforts in fine tuning Domino Release 5. In particular, we reviewed Show DBS output to monitor the performance implications of multiple Mail.Box files. While running benchmark tests, we evaluated the impact of increasing the number of available Mail.Box files, going from 1 to 4, and saw the average wait time decrease. The table output given above illustrates an example of a "well-behaving" production system (that is, we did not observe any real problems).

For more information on the Show DBS command, see the topic "Improving database and Domino Directory performance" in Domino 5 Administration Help.