bdowne01
New Member
Hi Everyone,
I'm a unix admin that helps manage a large character-based progress application (3000-3500 users). The application is structured in a way that the users connect to a front-end farm of servers (RedHat Linux), and use a remote connection back to a larger database server (AIX).
Our DBAs have configured the database to have a _mprosrv process for every 10 remote connections. The end result is the AIX server experiences extremely high kernel CPU% time, higher than user %--the end result being the server spins its wheels most of the time. IBM stated the kernel time is being generated by the large amount of _mprosrv processes.
So my question is what is the "best practice" for setting this up? Is there one? What should be a decent amount of _mprosrv processes to handle 3000 remote connections?
Thanks everyone!
I'm a unix admin that helps manage a large character-based progress application (3000-3500 users). The application is structured in a way that the users connect to a front-end farm of servers (RedHat Linux), and use a remote connection back to a larger database server (AIX).
Our DBAs have configured the database to have a _mprosrv process for every 10 remote connections. The end result is the AIX server experiences extremely high kernel CPU% time, higher than user %--the end result being the server spins its wheels most of the time. IBM stated the kernel time is being generated by the large amount of _mprosrv processes.
So my question is what is the "best practice" for setting this up? Is there one? What should be a decent amount of _mprosrv processes to handle 3000 remote connections?
Thanks everyone!