|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
Dual CPU opteron 252, 16 Gb ram, and SuSE Linux 10.1.
|
|
Issue Links:
|
Relate
|
|
|
|
This issue is related to:
|
|
|
|
|
|
CORE-937
Change default lock manager settings -- increase table memory and number of slots
|
|
|
|
|
|
|
|
In our current Firebird system (Classic FB 1.5.3), we have the hash slots value in the lock manager set to the maximum. Even with this, fb_lock_print indicates that we are close to the recommended figures of hash lengths. (Hash slots: 2039, Hash lengths (min/avg/max): 9/ 19/ 31.) We expect our database processing load to increase 5 to 10 times, so we will need the max hash slots limits increased appropriately (i.e., around the 32K mark).
|
|
Description
|
In our current Firebird system (Classic FB 1.5.3), we have the hash slots value in the lock manager set to the maximum. Even with this, fb_lock_print indicates that we are close to the recommended figures of hash lengths. (Hash slots: 2039, Hash lengths (min/avg/max): 9/ 19/ 31.) We expect our database processing load to increase 5 to 10 times, so we will need the max hash slots limits increased appropriately (i.e., around the 32K mark). |
Show » |
|
Improvement
Resolved
Increase the maximum number of hash slots for the Lock Manager