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

Performance regression when restoring database with big metadata [CORE2634] #3042

Closed
firebird-automations opened this issue Sep 18, 2009 · 6 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @AlexPeshkoff

Relate to CORE3079

Restore of metadata only backup for database with about 100 000 records in RDB$FIELDS runs approximately 20-25 times longer on 2.X compared with 1.5.

According to Dmitry, the reason is new type of deferred work, added in 2.0, which is posted after any insert of the record into RDB$FIELDS table. Time is wasted when workign with DFW is stored in linear linked list.

Commits: b19dace d1d8b30 57b4001

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

Fix Version: 2.1.4 [ 10361 ]

summary: Performance regression when restoring database with bug metadata. => Performance regression when restoring database with big metadata

@firebird-automations
Copy link
Collaborator Author

Modified by: @AlexPeshkoff

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

resolution: Fixed [ 1 ]

Fix Version: 2.5 RC1 [ 10362 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

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

@firebird-automations
Copy link
Collaborator Author

Modified by: @hvlad

Link: This issue relate to CORE3079 [ CORE3079 ]

@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