I know that a three tiered solution would make sense, but right know it is
just not an option since we don't have the time to rewrite the application -
it has to be in production by August!

I should have mentioned a few words about the application. It is fairly
simple application used in the Danish public sector to keep track of what
schools young people attend and what companies they work for. Each region in
Denmark is administered separately so it is fairly easy to assign a
different databases to different regions. Do you think it would make sense
to do that and buy two more back end servers so that the maximum number of
concurrent users would never exceed 140 on each server? The largest region
has 100 concurrent users.

Regards
Jan

----- Original Message -----
From: ""Alan McDonald"" <alan@...>
Newsgroups: egroups.ib-support
To: <firebird-support@yahoogroups.com>
Sent: Friday, June 18, 2004 3:13 PM
Subject: RE: [firebird-support] FireBird in a heavy load environment


> > My company is about to implement a rather large installation which
> > has to deal with up to 400 concurrent users. Our environment is as
> > follows. We have bought 4 front end servers running an IBX-app on a
> > Windows Terminal Server 2003 (100 users / server), one server
> > working as domain controller and one back-end server. The back-end
> > server is a Win2003 server dedicated to running the FireBird
> > (superserver). My question is, and I know it is a tough
> > one, can I expect to run into performance problems when dealing with
> > 400 concurrent users on 1-2 large databases (approximately 100 MB - 1
> > GB in size). The back end server is quite powerfull (2 x XEON 2.9 and
> > 3 GB RAM, RAID-5). I know that I have to set CPU-affinity so that the
> > OS and the database runs on separate processors.
> >
> > I am really interested in knowing whether anyone has experiens in
> > running FireBird in a similar environment. (By the way I have read
> > the user stories at IBPhoenix.com but I noticed that most of the
> > companies didn't have a large number of concurrent users).
> >
> > Regards
> > Jan Jensen
>
> together with Phil's comments, I would also have a backup plan of a 3 tier
> approach as well. 400 simultaneous users can be more easily supported with
> an application layer.
> Alan
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>