Skip to content
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

Improve performance of database file growth after CORE-1228 was fixed [CORE1469] #1886

Closed
firebird-automations opened this issue Sep 18, 2007 · 7 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @hvlad

Is related to CORE1228
Jira_subtask_outward CORE1478
Jira_subtask_outward CORE1479
Relate to CORE4443
Block progress on CORE4445

CORE1228 introduced one aditional write of every new allocated page to ensure there are space on disk for it.
This degrade performance when FW = ON. It can be improved if new pages will be written in relatively large groups.
Testing show that one single write of 128-512KB is much faster then 16-64 writes by 8KB

Commits: 6f28a5e 44c11df

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

Link: This issue is related to CORE1228 [ CORE1228 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Workflow: jira [ 13091 ] => Firebird [ 13950 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

Link: This issue relate to CORE4443 [ CORE4443 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

Link: This issue block progress on CORE4445 [ CORE4445 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

QA Status: No test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants