| Subject | Re: multithreading status (with jdbc2 connections) |
|---|---|
| Author | Adam |
| Post date | 2006-10-03T04:28:05Z |
--- In firebird-support@yahoogroups.com, "benow74" <andy@...> wrote:
The client library is not threadsafe, but all that means is that each
thread needs its own connection.
If you have a multi-cpu environment, then Classic Server tends to make
better use of SMP than Superserver, but Superserver shares a cache
between connections so there is no simple answer, just test it and use
the one which gives the best performance in your environment.
There may or may not be specific issues to jdbc, I would suggest you
ask on that list.
Adam
>What specific issues do you refer to?
> Hello all,
>
> I'm investigating the use of firebird for some performance intensive
> applications and have heard that there are issues with multithreaded
> access. Are those issues still there? How would it deal with a multi
> cpu/multi core environement? Any multi-threading issues with jdbc
> type 2 (native) database connections?
>
The client library is not threadsafe, but all that means is that each
thread needs its own connection.
If you have a multi-cpu environment, then Classic Server tends to make
better use of SMP than Superserver, but Superserver shares a cache
between connections so there is no simple answer, just test it and use
the one which gives the best performance in your environment.
There may or may not be specific issues to jdbc, I would suggest you
ask on that list.
Adam