-
-
Notifications
You must be signed in to change notification settings - Fork 233
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Increase the maximum number of hash slots for the Lock Manager [CORE958] #1360
Comments
Modified by: @dyemanovFix Version: 2.1 [ 10041 ] assignee: Dmitry Yemanov [ dimitr ] Version: 2.1 [ 10041 ] => |
Modified by: @dyemanovissuetype: New Feature [ 2 ] => Improvement [ 4 ] |
Commented by: @dyemanov The limit has been increased up to 64K. |
Modified by: @pcisarWorkflow: jira [ 11263 ] => Firebird [ 15360 ] |
Modified by: @pavel-zotovQA Status: No test |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: No test => Cannot be tested |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Submitted by: Greg Kay (glkay)
Is related to CORE937
Is related to QA109
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).
Commits: 70730a1
The text was updated successfully, but these errors were encountered: