| Subject | Re: [firebird-support] Help: firebird and apache Processes doesn't die |
|---|---|
| Author | Paul Beach |
| Post date | 2017-01-10T14:50:13Z |
<<I tested it many times: after stopping Apache server, the quantity of Firebird processes decrease to 2, but the memory isn't
released. Running "top -u firebird" command displays a lot of memory ( nearly 2 GBytes ) consumed by Firebird.
Is this a bug in Firebird Super Server or it was designed this way ?>>
SuperServer wil hold cached data as long as any connections exist. Only when the last "real" user disconnects
from the database will the cache be cleared.
Which two users are still connected to the database? CACHE WRITER and GARBAGE COLLECTOR?
If so then these should also finish with the last user connection.
Paul
released. Running "top -u firebird" command displays a lot of memory ( nearly 2 GBytes ) consumed by Firebird.
Is this a bug in Firebird Super Server or it was designed this way ?>>
SuperServer wil hold cached data as long as any connections exist. Only when the last "real" user disconnects
from the database will the cache be cleared.
Which two users are still connected to the database? CACHE WRITER and GARBAGE COLLECTOR?
If so then these should also finish with the last user connection.
Paul