| Subject | Re: [firebird-support] performance problem after "large" deletes (bug?) |
|---|---|
| Author | Helen Borrie |
| Post date | 2004-11-22T11:19:32Z |
At 11:37 AM 22/11/2004 +0100, you wrote:
Yup. The first user to select from that table after the huge deletes cops
the garbage collection.
What you really need to do following these big deletes is to run a
sweep. It will slow things down for a while but it avoids landing one user
with the big cleanup. It will also be a good idea to run SET STATISTICS
after the sweep, as well, then log out, then log in again.
Ideally, you wouldn't set out to run this kind of major housekeeping on
regularly used tables during busy times.
./heLen
>hi all,<....loooong report....>
>
>we are here experiencing some serious performance issues with one of
>our db applications ...
>
>the problem initially showed up on a fb1.0 database running on linux 2.4;
>however further tests showed that it is also reproducible on fb 1.5.1
>(linux 2.6, windows xp), 1.5.2.4634 (linux 2.6, fbsd 5.3) ..
>
>situation is as follows:
Yup. The first user to select from that table after the huge deletes cops
the garbage collection.
What you really need to do following these big deletes is to run a
sweep. It will slow things down for a while but it avoids landing one user
with the big cleanup. It will also be a good idea to run SET STATISTICS
after the sweep, as well, then log out, then log in again.
Ideally, you wouldn't set out to run this kind of major housekeeping on
regularly used tables during busy times.
./heLen