Subject | Re: Oldest Snapshot slowing down DB |
---|---|
Author | imoffskating |
Post date | 2006-02-08T09:46Z |
Thank you for your reply,
yes firebird does seem to hog 100% of the cpu, and restarting firebird
sorts everything out resetting oldest snapshot back to the same as
oldest transaction.
Do you think turning sweep interval on would help? and how do i do this?
Thanks again,
Alex
yes firebird does seem to hog 100% of the cpu, and restarting firebird
sorts everything out resetting oldest snapshot back to the same as
oldest transaction.
Do you think turning sweep interval on would help? and how do i do this?
Thanks again,
Alex
--- In firebird-support@yahoogroups.com, "Adam" <s3057043@...> wrote:
>
> I am not sure what oldest snapshot means, but these two are the
> general indicator of database health.
>
> > Oldest transaction 9181346
> > Oldest active 9181347
>
> In this case it looks good to me, the gap is < 20000.
>
> Perhaps someone else could shed some light on your issue, and why a
> restart may help. Is it possiblly a resource thing? As in is the CPU
> pegged at 100% due to some intensive operation? Restarting the server
> will obviously stop this operation which may explain why performance
> comes back.
>
> Adam
>