System Resource Bottlenecks: If your site has not maxed out either CPU utilization, database server utilization, or I/O subsystem, the problem may result from synchronized access to one of your system's resources (disk, network, database, etc.). This situation occurs when you access this resource from within a synchronized method in Java. All other requests wait for this monitor lock while you do the I/O, thus wasting both CPU and I/O resources.
The only ways around this problems are to recode the Java (the right solution) or add more App Server instances (the wrong solution).
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment