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

GBAK using only 1 CPU Core [CORE3958] #4291

Closed
firebird-automations opened this issue Oct 22, 2012 · 12 comments
Closed

GBAK using only 1 CPU Core [CORE3958] #4291

firebird-automations opened this issue Oct 22, 2012 · 12 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Yordan Yanakiev (yordan1)

Duplicates CORE1365
Duplicates CORE2992

GBAK is using only 1 core, which on databases larger than 120 GB tooking more than 10 hours to complete.

During this time the whole company having downtime, which recently became each month, which is frustrating.

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

First of all, this is not a bug. Second, I suppose you're talking about restore, not backup? Why do you restore the database monthly?

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

security: Developers [ 10012 ] =>

@firebird-automations
Copy link
Collaborator Author

Commented by: Yordan Yanakiev (yordan1)

There is too much garbage left while operating, the database performance significantly decreasing ( like 2000-3000% ) and it is fixed after backup/restore procedure.
Why it isn't bug since it is supposed to utilise maximum all of the cores ?
And one more question - which would be better - Intel i7-3370k processor ( 4 cores on 3.5 GHz ) or AMD Opteron ( 16 cores on 2.2 GHz ) for GBAK backup/restore procedures, since we goin to buy a server which to fix a bit this frustration while there is found a fix for this bug.

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

You don't need backup/restore to clean up the garbage, this task is accomplished by other tools.

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

Link: This issue duplicates CORE1365 [ CORE1365 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

Link: This issue duplicates CORE2992 [ CORE2992 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

Closed as a duplicate (see CORE1365 and CORE2992).

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

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

resolution: Duplicate [ 3 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

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

@firebird-automations
Copy link
Collaborator Author

Commented by: Yordan Yanakiev (yordan1)

the duplicates is not a solution to the bug.

@firebird-automations
Copy link
Collaborator Author

Commented by: sarah (sarah.mcmurray)

sorry to be obtuse but how do you fix this problem? its 330am and i'm totally f**cked off waiting for 4 x 2 hour backup and restores with 1 core full tit, disk usage low - how do i make interbase use all the cores?

@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

1 participant