> > There is very little documentation available on the Classic lock
> > manager related settings, which is why I ask the question in this forum.
> > Interested in v2. 5 limitations, but details/differences for other
> > versions would be appreciated.
>
> I assume you mean hash table slots:
>
> const SLONG HASH_MAX_SLOTS = 65521;
That was what I was looking for?
Is there any reason why for x64 builds that number could not be increased?
We are facing a situation at our largest install where the lock print results
are showing Mutex wait % of 34.
Was wondering if increasing the number of slots would reduce the wait %.
The lock print results are:
LOCK_HEADER BLOCK
Version: 145, Active owner: 0, Length: 50331648, Used: 37221720
Flags: 0x0001
Enqs: 1533920191, Converts: 16196704, Rejects: 2691693, Blocks: 41288728
Deadlock scans: 511, Deadlocks: 0, Scan interval: 10
Acquires: 2133945841, Acquire blocks: 730378904, Spin count: 0
Mutex wait: 34.2%
Hash slots: 62989, Hash lengths (min/avg/max): 0/ 0/ 6
Remove node: 0, Insert queue: 0, Insert prior: 0
Owners (263): forward: 516680, backward: 7557912
Free owners (462): forward: 25406352, backward: 23232448
Free locks (31805): forward: 12342808, backward: 3613624
Free requests (344561): forward: 13926664, backward: 26670520
Lock Ordering: Enabled
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
