Olivier,

> Using version 2.5, embedded, windows.
> Application server process is multi-threaded, one thread per user.
> Each of these threads use a distinct attachment (and hence distinct
> transactions, statements, ...).
> Considering using a single attachment (per DB, per server process), shared
> among those threads, but still keep thread isolated transactions, statements,
> and so on...
>
> I'm wondering how much contention will happen between all these threads
> sharing a same attachment, but using distinct transactions and statements
> handles.

If you use a single attachment, then your commands will be serialized -- not good if you expect/need simultaneous operation.

Each thread needs its own attachment/connection.

There is very little overhead, however, for each connection.


Sean