Subject | Re: [firebird-support] slow query at first execution |
---|---|
Author | Marco Parmeggiani |
Post date | 2004-04-30T10:58:39Z |
In data Mon, 26 Apr 2004 17:56:01 +0200, hai scritto:
1) I noticed that installations that claims to have problems are ususlly
running low on ram. I'm now investigating on some memory leak although it's
not easy to find who is stealing (if there is one). Does Firebird 1.0.x has
problems with memory allocations in some circumstances (maybe version under
1.0.3 have some bug (i have, sigh, some <1.0.3 dbms around)?
2) Usually, but not always, those database are poorly mantained and a
backup/restore run solves the problem. I think that this is a temporarly
solution as database is growing and growing but surerly is a necessary
operation to perform periodically.
3) Be careful from now on i'm trying to interpret the problem without
really knowing how things works behind the DBMS, so be patient please.
I think that the problem is given by the time needed to load a needed index
that, for memory reasons, cannot be kept in memory and it's unloaded if not
used for a certain amount of time. Is this possible?
If this is the case, can i avoid the dumping of some critical indices?
Mybe should i give my database a revision and try to dump some indices(i've
not created indeces randomly but, maybe, i can find some sacrificable one)?
Thanks for any suggestion
ciao
> I'm performing a very simple query (no joins) using a stored procedure on aI have more infos now:
1) I noticed that installations that claims to have problems are ususlly
running low on ram. I'm now investigating on some memory leak although it's
not easy to find who is stealing (if there is one). Does Firebird 1.0.x has
problems with memory allocations in some circumstances (maybe version under
1.0.3 have some bug (i have, sigh, some <1.0.3 dbms around)?
2) Usually, but not always, those database are poorly mantained and a
backup/restore run solves the problem. I think that this is a temporarly
solution as database is growing and growing but surerly is a necessary
operation to perform periodically.
3) Be careful from now on i'm trying to interpret the problem without
really knowing how things works behind the DBMS, so be patient please.
I think that the problem is given by the time needed to load a needed index
that, for memory reasons, cannot be kept in memory and it's unloaded if not
used for a certain amount of time. Is this possible?
If this is the case, can i avoid the dumping of some critical indices?
Mybe should i give my database a revision and try to dump some indices(i've
not created indeces randomly but, maybe, i can find some sacrificable one)?
Thanks for any suggestion
ciao