This week's giveaway is in the Android forum.
We're giving away four copies of Android Security Essentials Live Lessons and have Godfrey Nolan on-line!
See this thread for details.
The moose likes BEA/Weblogic and the fly likes Need the reason Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "Need the reason" Watch "Need the reason" New topic

Need the reason

babu sh

Joined: Mar 06, 2010
Posts: 2
Most of the Servers speed is good whenever there are number of users & speed is slow whenever there are a few users.
what is the reason?
Joe Ess

Joined: Oct 29, 2001
Posts: 8843

It is impossible to give you a good answer without knowing the intimate details of your deployment environment.
My employer has an application that exhibits this kind of behavior. The developers blame it on load balancing, that until a certain load threshold is reached, the resource pools (caching, database pool, etc) are not fully initialized so performance suffers. Which begs the question, why don't they set an idle threshold rather than let all those resources expire only to reinitialize them for the next user.

"blabbing like a narcissistic fool with a superiority complex" ~ N.A.
[How To Ask Questions On JavaRanch]
Joseph Antoine Raja
Ranch Hand

Joined: Feb 01, 2010
Posts: 32

The answer is simple

when the less no of process and users are in server the CPU load/utilization will be low so your server process will utilize the maximum resources and events will be faster.

in case of too much of request and process the server has to wait for commit the events which will result in slowness.

It is sorta covered in the JavaRanch Style Guide.
subject: Need the reason
Similar Threads
WA #1.....word association
Exception Handling
WA #2 ..... word association
DVR's Save Time
System Inventory Application/JSP