On Mar 4, 2008, at 11:31 AM, Klaus Berkling wrote:
I maintain two WebObjects installation in China.One of them is giving me problems - performance is slow. Our users can't get connected, yet there are many sessions and much activity in the logs.I have 80 instances for 2 servers, they handle 10-30 sessions each. Requests are completed usually in less the 1 second.- Maximum Adaptor Threads is 512Increasing this correlates to increasing incoming connections to the HTTP server.- Listen Queue is 2It was 10, I don't want too many people in the queue to start any sessions when the user ends up quitting and trying again - therefore ending up with two sessions were one is left to timeout.
Listen Queue is actually a low-level TCP thing.Adaptor threads is the number of threads to spawn to service your requests.
You seem to have those two settings switched, typical TCP listen queue is something like 128, with adaptor threads more like 8-16 at most. If you're spawning 80 instances with up to 512 worker threads each, it would surprise me if your app would run at all.
You can adjust your session timeout dynamically. We allow 5 minutes to login, but once you login, we bump it back up to 3600. That way we don't have a bunch of stale sessions triggered by web robots.
- Session timeout is 10 minutes For Adaptor settings: - I'm using Load Average to balance the load.
Load average is inherently broken. Use Round Robin.
- Send timeout is 10 seconds.- Receive timeout is 600 seconds since we may execute queries that take some time, very rare.- Connect timeout is 10 seconds.
Those are ok, though browsers may timeout before the 10 minutes are up.
- Connection Pool is 2
Connection pooling only works with certain webservers, and apache is not one of them.
I might get 300-400 concurrent connections to the web server. I should be able to handle that.The WO servers never see high CPU load and have 25% inactive RAM available.On the database server, there is no sustained high CPU load.I'm using InnoDB. My ibdata file is 20GB - I assume this to be very large.
Databases are generally I/O bound, not CPU bound. WO apps are generally database bound, not CPU bound.
To me these numbers are contradictory but these are the numbers. Any thoughts? Anything that blatantly wrong with this?
Well, yes.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-deploy mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
