Subject | Re: Automatic garbage collection? |
---|---|
Author | smart@mrbit.es |
Post date | 2001-10-26T10:48:43Z |
Hi Paul, thanks for your answer. Some notes.
"Paul Reeves" <paul@...> wrote:
to edit many many procedures.
Aren't there some method to disable this "background garbage
collection"?
If no solution I will try to get the Firebird source code, edit,
compile and pride...
Does somebody known where/when the garbage collection
is "automatically" activated?
Omar
"Paul Reeves" <paul@...> wrote:
> Omar Estepa wrote:(after mass
> >
> > Hi,
> >
> > We was having problems with our Linux database server (about 6 GB,
> > IBSS_LI-V6.0), it seems to be overloaded by garbage collection >>
> > deletion, I think). No problem, I go to our backup/restore dailyscript and
> > add the "-g" option to gbak commands and it works fine. Thedatabase check
> > tells me everything is OK and backups works fine (with "-g").should only
>
> gbak -g causes gbak to run with garbage collection disabled. You
> add this switch if you are going to use the subsequently restoreddatabase in
> production.Yes. That's right.
> > But few days later we have de same problem, the server slows downagain
> > (100% CPU time usage) when the users was working (nobackup/restore process
> > was running at this time). Auto-sweep is turned off.OK.
>
> You shouldn't turn auto-sweep off in 6.0. That was a v4/v5 thing.
> > Can the IB server automatically run the garbage collection? If itcan, can I
> > dissable this feature? Does anybody have another idea?collection.
>
> V6 saw the introduction of background threads to handle garbage
> You really shouldn't need to change sweep from its default value.look at.
>
> If you are doing mass deletes then there are a couple of things to
> Firstly, if the contents of the entire table are to be deleted thendropping
> the table and recreating it is cheaper than deleting records. Thereis even a
> new command in Firebird to assist this.disabling the
>
> If you are not deleting all the records in a table then look at
> non-system indexes on the table prior to the delete and activatingthem again
> when the delete has been committed.Hummm. That's not a good solution in our situation.... We should need
to edit many many procedures.
Aren't there some method to disable this "background garbage
collection"?
If no solution I will try to get the Firebird source code, edit,
compile and pride...
Does somebody known where/when the garbage collection
is "automatically" activated?
Omar