mutil_lib connection count

System

Hi,
we have a customer use worksitemp to manage multiple libraries, totally 32 libraries to suppport total 1000 users. every library support one branch users, max 50 users. DBMS is oracle.
we setup all labraries on a worksitemp cluster(2 servers with 2cpus),every library have one oracle tablespace to store all tables. we setup lib connection number to 2 for every lib. that means totally 64 connection will be created in Oracle server when worksitemp run. but 2 connection for one branch users is not enough, concurrent branch user could be 5 timers than connection settings. if we setup 10 connections for every lib, there will be 320 connections totally .

WSMP occupy almost all of connection in Oracle server,
No available user can connect to the server When WSMP are starting.

my quesiton is :
1. connection between every lib can be shared to use by every lib ,or only used by the single lib? if one lib only have 2 exclusive connections to support 50 users, the connection is definitely not enough! if total 64 connection can be shared to suppport 1000 users, it will be better.

2. what's the realtion between the conneciton setting in wsmp web component and conection number in cluster settings? what if we use multiple lib in web component?

3. what's you suggesiton for above situation?


any help is appreciated!

Migrateduser

I can share some data from internal performance tests.
(Disclaimer: I cannot guarantee the accuracy of this data. There are a lot of variables that control the numbers posted below. This data is not derived from any document published by Interwoven. Please use them as guidelines, at your own risk.)

20 DB connections are enough to support 800 concurrent users (with 60 seconds think time between page clicks) on a 1-1-1 stack (one webapp, one CMS and one DB, all quad Xeon 3.66GHz processors). The pages per second is 14. Though the number of webapp-to-CMS connections configured is 50, the max used is generally less than 20, if I remember correctly. You can check your WOM logs to get this number for your production server.

60 DB connections in total are sufficient to support 1800 users (with 60 seconds think time) on a 1-2-2 stack (one webapp, two CMS servers, two DB machines, all quad Xeon 3.66GHz processors). Pages pers second is ~28. Number of connections. The number of webapp-to-cms connections is still 50 per library. Note that the number of DB connections specified in config manager cluster configuration dialog is 15. This number is multiplied by number of CMS servers in the cluster and the number of librarires. (2 x 2 x 15 = 60).

My gut feeling is that two DB connenctions per library might be more than enough for five concurrent users. If you specified two in the config mgr, the actual connections used up are four (each cms server makes two db connections).

May I ask why you need to setup 32 different libraries for 1000 users?