Adam,

The appserver is Apartment threaded COM object. And there is no
bottle neck I am just trying to better understand the differences in
classsic and superserver. Right now we are using IB 6 but it will
not scale. And for most of our client base the Interbase 2007 cost
is to much. I have not tried the classic version only the
Superserver. Superserver does fine but does not appear to take
advantage of the multi-processor enviroment. Is there a problem
switching from classic to superserver or vice versa in a production
enviroment? I just want to know that we can scale with Firebird and
take advantage of these multi core machines.

Thanks, Todd

--- In firebird-support@yahoogroups.com, "Adam" <s3057043@...> wrote:
>
> --- In firebird-support@yahoogroups.com, "toddmxz" <todd7@> wrote:
> >
> > Hi,
> >
> > I now understand better where one of my problems lies. We use an
> > application server to connect to the database the application
server
> > make a single connection to the database thus making classic mode
not
> > feasable. Or at least not beneficial for us that I can tell. Is
work
> > being done to make Superserver mode support SMP in the model I
stated
> > above?
>
> Todd,
>
> Do you mean to tell me your application server is only single
> threaded? I hope so, because Firebird connections are not thread
safe,
> although a bunch of critical sections sitting in your application
> server would certainly explain performance bottlenecks.
>
> I mean there are a few possible SMP optimisations in a single query
at
> a time environment (eg. when union is involved), the big benefit of
> SMP is the capability to handle multiple queries simultaneously; a
> situation you do not have if you have established just a single
> connection.
>
> Adam
>