Okay, my db_stats, running BerkeleyDB 4.7.25, looks as follows (see
below). There's one thing I don't understand, though. It says:

"10 Lock requests not available due to conflicts,"

What does that mean, given that the 'Maximum number of lockers at any one
time' has only been 76? (out of a possible 2500). Or is it just saying
that it couldn't aquire a lock immediately? (like with flock on files).
The environment itself looks otherwise sane enough to me.

Thanks,

- Mark


0x7fffffff Current maximum unused locker ID
5 Number of lock modes
2500 Maximum number of locks possible
2500 Maximum number of lockers possible
2500 Maximum number of lock objects possible
1 Number of lock object partitions
0 Number of current locks
74 Maximum number of locks at any one time
5 Maximum number of locks in any one bucket
0 Maximum number of locks stolen by for an empty partition
0 Maximum number of locks stolen for any one partition
0 Number of current lockers
76 Maximum number of lockers at any one time
0 Number of current lock objects
21 Maximum number of lock objects at any one time
1 Maximum number of lock objects in any one bucket
0 Maximum number of objects stolen by for an empty partition
0 Maximum number of objects stolen for any one partition
1079171 Total number of locks requested
1079171 Total number of locks released
2998 Total number of locks upgraded
63234 Total number of locks downgraded
10 Lock requests not available due to conflicts, for which we waited
0 Lock requests not available due to conflicts, for which we did not
wait
0 Number of deadlocks
0 Lock timeout value
0 Number of locks that have timed out
0 Transaction timeout value
0 Number of transactions that have timed out
1MB 296KB The size of the lock region
0 The number of partition locks that required waiting (0%)
0 The maximum number of times any partition lock was waited for (0%)
0 The number of object queue operations that required waiting (0%)
0 The number of locker allocations that required waiting (0%)
4 The number of region locks that required waiting (0%)
1 Maximum hash bucket length