Monitoring 'Messages Received' & 'Sent' on WL console

Question

I'm running a stress test on a WL server 6.1 SP1 deployment.
Monitoring the client to server connections at peak usage, in the WL server console,
I find that the EJB server's default queue shows lopsided numbers:
Messages Received = 4644
Messages Sent = 1219
Messages Sent remains constant after maximum load and increases only towards the
end of the test when load is reduced.
Can someone throw more light on this?? What tuning may be required to improve
this ratio?
The application is doing mostly JDBC calls to the database. Most of the threads
in the execute queue are idle. The average CPU usage on the WL server machine
as well as the DB server is less than 10%.
Thanks in advance.
- Gagan

Answer 1

We'd need some more info before we can suggest how to tune or improve
the performance of your application.
I'd start by running a single client thread. If the performance of that
is not fast enough then start determining where it is spending its time
(eg in WL or in the database etc).
If a single client is fine, start ramping up to more clients until your
performance becomes unacceptable. At that point, I'd start with the
same gaim of recording info (eg cpu usage etc) and measuring times.
-- Rob
Gagan Bhatnagar wrote:
I'm running a stress test on a WL server 6.1 SP1 deployment.
Monitoring the client to server connections at peak usage, in the WL server console,
I find that the EJB server's default queue shows lopsided numbers:
Messages Received = 4644
Messages Sent = 1219
Messages Sent remains constant after maximum load and increases only towards the
end of the test when load is reduced.
Can someone throw more light on this?? What tuning may be required to improve
this ratio?
The application is doing mostly JDBC calls to the database. Most of the threads
in the execute queue are idle. The average CPU usage on the WL server machine
as well as the DB server is less than 10%.
Thanks in advance.
- Gagan