Dipesh wrote:

> We are using:
>
> Windows 2000 SP4
> Firebird-1.5.3.4870-0 SS
> Apache2 2.0.52
> PHP 5.1.2 (CGI-mode, with php_interbase.dll extension)
> gds32.dll in Windows/system32 generated by FB1.5.3 instclient.exe i g
> Database resides in c:\work\data and is aliased to alias1 in aliases.conf
>
> C:\WINDOWS\system32\drivers\etc\services has the line:
> gds_db 3050/tcp
>
> All of this is running on one machine,
> Everything is running ok while the load is lite.
> I can connect to the FB server just fine through isql or through php.
> But under heavy load (~90%+ cpu / 200+ concurrent database
> connections) we get the following behaviors:
>

I think the key here, is All of this is running on one machine.
Firebird and Apache are both memory heavy, and with that many
connections network heavy applications. Windows (any version), is a
resource hog as well.

Your better off running 2 machines one for Firebird and one for Apache,
if the Windows licence for a second machine is too expensive, run one on
a stripped down Linux ( install only the pieces that are absolutely
needed ). I would run Firebird on the Linux box, and run with only
Firebird and root (Administrator) as users. Essentially the database
server would be a black-box appliance, with lots of disk, lots of RAM,
good place for RAID drives, and only the database to use it all.

Often such Linux boxes run headless, there is no monitor, keyboard or
mouse hooked up, so nobody can goof with it. If you need to be able to
do maintenance, there is a package that works as a web interface, that
you can use, I forget the name of it.

Personally, I would run Apache on another box set up the same, but
that's just personal preferance, Linux is a lot better at that stuff
then Windows of any version.

W