I have experience with larger systems - 8,000 plus concurrent users,
but I have not done any large Firebird deployments yet.

If centralization is required, you will want to use classic on as large
a *nix box as you can get. There were issues with the 64 bit compiles.
I don't recall if those have been resolved.

1. How many transactions per minute?

2. What sort of applications are you proposing to run?


Common application design principles are simple.

Never hold a transaction open any longer than absolutely necessary.

Never hold transactions open while a user edits.

Always commit.

Data modeling is critical

Performance is a requirement, not a luxury. Design for performance.

dUnit (Delphi) jUnit (java) cxxUnit (C/C++) pyUnit (python) etcetera are
your friends. Test before coding.

On Tue, 2005-08-09 at 22:53 +0000, Eduardo A. Salgado wrote:
> --- In firebird-support@yahoogroups.com, Alexandre Benson Smith
> <iblist@t...> wrote:
> > I had never deployed a system for a thousand users, I think the
> maximum
> > I have are around 100-150 concurrent users.
> >
> > I think, when you have a lot of users, the best approach will be a
> > connection pool using a middle tier application.
> >
> > or
> >
> > Have 4 or 5 servers and use replication for syncing the data
> between then.
>
> Alexandre
>
> How are you doing your 100-150 concurrent users?
>
> I am quickly getting in beyond my pay grade ;-)
>
> Were do I go to learn about large numbers like these?
>
> Feel like the dog chasing the bus. Now that we caught it ...
>
> -Eduardo
>
>
>
>
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Visit http://firebird.sourceforge.net and click the Resources item
> on the main (top) menu. Try Knowledgebase and FAQ links !
>
> Also search the knowledgebases at http://www.ibphoenix.com
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Yahoo! Groups Links
>
>
>
>
>
>