Subject | Re: [ib-support] URGENT: API memory leaks! |
---|---|
Author | Ann W. Harrison |
Post date | 2002-02-11T14:25:12Z |
At 11:44 PM 2/10/2002 +0300, Lev Assinovsky wrote:
preparing a statement causes memory to be allocated in the
server to hold the compiled version of the statement. The
amount of memory is related to the record size of the table,
the size of the data returned, and the complexity of the query.
The memory is released to the server when the request is
released. Firebird/InterBase never return memory to the
system on the assumption that some other connection will
want to use memory and reusing allocated memory is cheaper
than reallocating it.
Regards,
Ann
www.ibphoenix.com
We have answers.
>Each nested SELECT allocates approx 24K - which is never returned.This is probably incredibly obtuse (i.e. stupid) of me, but
preparing a statement causes memory to be allocated in the
server to hold the compiled version of the statement. The
amount of memory is related to the record size of the table,
the size of the data returned, and the complexity of the query.
The memory is released to the server when the request is
released. Firebird/InterBase never return memory to the
system on the assumption that some other connection will
want to use memory and reusing allocated memory is cheaper
than reallocating it.
Regards,
Ann
www.ibphoenix.com
We have answers.