> Thanks for your prompt response.
>
>> The mutex wait relates to the amount of time transactions spend
>> waiting to make changes to the lock table. 64.6% is huge. 10%
>> is excessive. One reason for long waits is that the transaction
>> that has mutex for the table takes a long time to find the objects
>> it wants to change. It finds them by hashing on their identifier
>> and walking down the hash chain until it finds the right object.
>> If there's only one object in the hash chain, that's quick. If
>> there are 22, that's a problem.
>>
>> Increase your hash table size.
>
> I will have that changed to 2039. (Presumably the service needs to be restarted for changes to take effect).

Not in Classic. The next connection immediately gets the changes in
firebird.conf.


--
Best Regards,
Thomas Steinmaurer
LogManager Series - Logging/Auditing Suites supporting
InterBase, Firebird, Advantage Database, MS SQL Server and
NexusDB V2
Upscene Productions
http://www.upscene.com
My blog:
http://blog.upscene.com/thomas/