Subject | Re: [firebird-support] backup very slow and how often sweep a database ? |
---|---|
Author | Thomas Steinmaurer |
Post date | 2011-12-21T08:08:32Z |
> it's a disaster .... i disable the gfix -sweep every night and launch itFind the reason why you produce such a transaction gap within 5 hours.
> only when the difference between oldest transaction and next transaction
> is> 20 000 but this become true only after 5 hours :( so at the end
> everyday the difference between oldest transaction and next transaction
> grow by more than 20 000 :(
>
> i can not run gfix everyday, it's took hours to finish :(
>
> what i can do ?
Is it just the OIT which is behind or OAT as well? What's the output of
gstat -h?
If OAT as well, then you have a long-running transaction or using commit
retaining over and over again.
If you are using Firebird 2.1, then use the MON% tables to investigate
running transactions. If you are using Firebird 2.5, then use the MON%
tables and/or the Trace API to investigate the problem.
Regards,
^TS^
> stéphane
>
> On 12/20/2011 8:41 PM, Ann Harrison wrote:
>>
>> Stéphane,
>>
>>> the probleme is that the sweep can take up to 5 hours to finish and the
>>> backup up to 12 hours to finish :(
>>> i know that in the backup i don't put the -g params (inhibit garbage
>>> collection) but someone say me that
>>> the -g do something else that the gfix.exe -sweep doesn't do ...
>>
>> As others have said, sweep does something that gbak doesn't. Specifically,
>> sweep resets the "oldest interesting transaction" - the first
>> transaction in the
>> system that may have rolled back leaving changes in the database. Keeping
>> that number accurate was very important a decade ago when memory was
>> expensive and rare and Firebird did not automatically undo changes when
>> a transaction rolled back leaving the server alive.
>>
>> When reading records, Firebird must check the state of transactions newer
>> than the oldest interesting. At startup, Firebird produces a bit
>> vector of those
>> transactions where each pair of bits indicates the transactions state:
>> rolled back,
>> committed, limbo, or active. The shorter the vector, the better, but
>> 64K bits
>> isn't as interesting as it was a decade ago.
>>>
>>> now i need to know, how often i need to launch the gfix.exe -sweep and
>>> the gbak.exe -B without the -g params ? everydays seam not anymore
>>> possible because of the time taken
>>> by these process...
>>>
>>> one time a month ?
>>>
>> Backup as often as lets you sleep at night. Sweep once a week if possible,
>> once a month if not.
>>
>> Good luck,
>>
>> Ann
>>
>>
>
>
> [Non-text portions of this message have been removed]
>
>
>
> ------------------------------------
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Visit http://www.firebirdsql.org and click the Resources item
> on the main (top) menu. Try Knowledgebase and FAQ links !
>
> Also search the knowledgebases at http://www.ibphoenix.com
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Yahoo! Groups Links
>
>
>