Thanks guys, that is some interesting and useful information.

Regards, Bernard

--- In firebird-support@yahoogroups.com, "Nigel Weeks" <nweeks@e...>
wrote:

> Yes - you can end up with one database process per apache httpd
> process...for a highly loaded server, 200 httpd's means 200
> firebirds...might start wading into swap.
>
> There's a trick - recycle your apache processes...
> in your httpd.conf, there's a setting 'MaxRequestsPerChild'. It's

usually

> 0(infinite), which never recycles child processes.
> Change this to 5000 or so - it means pconnects are dropped after a

while,

> and memory can be freed up.
>
> Tune this to match your situation - you might find limiting the

number of

> httpd processes it another way of keeping out of swap(don't go too low -
> you'll prevent people getting connections at all)
>
> N.
>