C
ChUIMonster
Guest
FUD aside, running hundreds of users with shared memory connections is very common in the UNIX world. It is not all that risky. And it does indeed perform much better than client-server does. You have to avoid "kill -9" to avoid the dreaded crash while holding a latch but that really isn't all that hard. And the benefits are substantial. (It is also cheaper because you do not need a "client networking" license...) The main risk is know-nothing sysadmins whose approach to all problems with the "kill -9" hammer because they mistakenly believe that "it always works". If your company employs such a person you might want to ask HR to update their hiring matrix to ensure that the next sysadmin is a bit more qualified. Windows is challenging because there are many things that happen in the Windows world that are effectively a "kill -9". Like killing a process with task manager. Or having your background jobs killed for you when you logout. So there is reason to be concerned if you must live in that world. App servers are intended to provide a way to get the best of both worlds. If your ADM code makes use of app servers then it might be sufficient to move those to the db server and run them as shared memory connections. That avoids the end-user misbehavior problems while gaining the benefits of shared memory connections. If your code does not use app servers and you don't want to change that you're kind of stuck. Rob's general points about tuning are a good starting place. There are also a bunch of useful things that can be done with regards to the client/server connections themselves. -Mm and -prefetch* are good starting points. If you need more help I know people who would be happy to help with the details on a professional basis 
Continue reading...
Continue reading...