If this was a memory leak, removing the process from memory will NOT
return consumed memory back to free space, at least not initially
(Nowadays, operating systems are pretty good about cleaning this up,
though it is never immediate).

Jason

rodrigogoncalves wrote:

>
> Long-running transactions indeed is a problem with the software...
> much of it is legacy code (badly use of IBX or even using BDE) so I'm
> reviewing the code and changing it all to shorter transactions and
> more use of clientDataSet components.
>
> But I have the feeling that in the case of this server it may be some
> problem between the Fedora Core 3 and Firebird, which leads to a
> memory leak (looking at the memory status, I see that 400mb of memory
> is used by applications and only a 100mb is being used by cache, so I
> assume Firebird is using a lot of memory...). Sweeping manually the
> database also brings the memory usage down by only a few megabytes.
>
> I'm going to try a self-compiled Firebird and see if it gets better.
> My only problem is stopping the server, since it's a 24x7 one... *sigh*
>
>
> Anyway, tks for the answers
>
> Regards
> Rodrigo
>
>
>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Visit http://firebird.sourceforge.net 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
>
>
>
>
>
>
>
>
>