>
> I doubt it...
>
> I have a costumer running FB 2.0 SS on a Windows2003 box, server is P4
> 1Ghz 1GB RAM. This setup is serving around 60 users.
>
> I have others running SS on Linux machines serving around 15-20 users
>
> Everything depends on how you write your app, once CS has separated
> process for each connection, no one would being "stopped" to work if

one

> connection requests a very slow statement. The OS scheduler will

handle it

>
> Some questions... how do you handle your transactions ? could you show
> us the database statistics when you find your database slow ?
>
> Could you show us a typical statement that you think is slow and the
> execution plan ?
>
>

The database in question handles connections from a variety of sources
from sql queries run by ISQL from bash scripts to PHP on web /
intranet servers and legacy Windows apps like MS Access & Visual basic
programs.

I suspect it is the interaction with MS Access that causes the most
problems.

However the problem is real.
The classic server works without obvious slowdown all the way up to
its ~ 60 user peak. Once past about a dozen users the superServer
starts to stall.

I can't attempt to diagnose the problem for obvious reasons.