evan@... wrote:

> Just found another thing. In hammering the server with a thousand different
> ibase_connect and ibase_close statements in under 40 seconds, and viewing
> the processes in top on the database machine, there are actually only a few
> gds_inet_server processes that open. Not a thousand. Maybe four or five max.

Top doesn't refresh that fast.

How exactly are you hammering it?
Do you just connect, or query?
Can you show us some code, and describe what exactly you are doing?
Do you get the reply for all these requests?
Are you "hammering" though Apache, or calling php directly?

Besides, AFAIK, calling ibase_connect more than once in the same php
file with the same params does nothing.

> What's also interesting is that they mostly go away, except - usually - one,
> that hangs around even when there are no queries being executed. It just
> hangs out there and then *consumes CPU* resources, even if *no queries are
> being executed*.

It seems like you're running Classic. The only process that you could
have running all the time is gds_lock_mgr

At the end, prehaps you are simply issuing some "heavy" query that hogs
the db. You could make a log file (simple txt file) where you would
write every sql before executing it, and when the problem happens, just
read the last query from that file.


--
Milan Babuskov
http://fbexport.sourceforge.net