I'm looking at around 250-300 simultaneous users, nearly all of them doing interactive work. (Curses-based screen stuff for the most part) I'd not too worried about the server we've got for them being able to handle that except... for reasons that are fairly annoying, I'm looking at somewhere in excess of 9K simultaneous connections to the database server, and I'm not in a position to cut that down any. (The app suite's written in an old 4GL that assumes an ISAM database. We're porting to a modern database and runtime, but we have to preserve the DB semantics of the original database. Nasty, but there you go)
I know each of the back-end processes is going to suck down some resources on the server, but am I going to hit coordination or inter-process sync delays with that many different back ends going at once? (And is there a good way, short of just running some load tests, to estimate the costs involved?)
--
Dan
--------------------------------------it's like this-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
