> If it's tied up in isc_dsql_prepare then my whole architecture is
> broken. Prepare should only occur when a pool connection is constructed
> (i.e. at startup), not during operation. Remember that odd pattern of
> usage that exposed a bug in classic? That was the bit that guarantees I
> should never hit a prepare during operation.

Then maybe this behavior is ok. I was just surprised that removing the TCP
stack brought only 13% on a data intensive application.

Roman