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.
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*.

Hmmm.