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?
to your account
Submitted by: @asfernandes
Relate to CORE3802
There is a simple change which makes it much faster, tested with Linux 2.5 embedded restore:
Two databases, with two different tables filled with 2,000,000 records:
create table t1 (n1 integer);
create table t10 (n1 integer, n2 integer, n3 integer, ..., n10 integer);
Improved gbak timings:
GBAK builts a BLR in the following way:
Then calls isc_start_and_send N (records) time.
My change creates this BLR:
Calls isc_start_and_send first time then N-1 isc_send.
Commits: b269d8b bf51ab2 e53330f
The text was updated successfully, but these errors were encountered:
assignee: Adriano dos Santos Fernandes [ asfernandes ]
Sorry, something went wrong.
Commented by: @dyemanov
I've changed the title to better reflect the goal of this fix. There are other possible improvements, e.g. related to index creation performance, and it'd be better to have these changes outlined/logged as separate items.
summary: Improve GBAK restore performance => Improve GBAK restore performance (records insertion)
status: Open [ 1 ] => Resolved [ 5 ]
resolution: Fixed [ 1 ]
Fix Version: 2.5.1 [ 10333 ]
Fix Version: 3.0 Alpha 1 [ 10331 ]
Commented by: @alexeykovyazin
Can I ask to back port it to 2.1.5?
There are some big databases running on 2.1.4 (up to 400Gb), and having several % of improvement will save many minutes of maintenance.
Commented by: Thomas Steinmaurer (tsteinmaurer)
I would also like to ask whether it is possible to back port this improvement into 2.1.5. Thanks!
Commented by: @asfernandes
Probably yes. I'll check it.
Backported to 2.1.5.
Fix Version: 2.1.5 [ 10420 ]
Link: This issue relate to CORE3802 [ CORE3802 ]
status: Resolved [ 5 ] => Closed [ 6 ]
status: Closed [ 6 ] => Closed [ 6 ]
QA Status: Cannot be tested
Successfully merging a pull request may close this issue.