Re: Thread or no thread
Re: Thread or no thread
- Subject: Re: Thread or no thread
- From: Robert Walker <email@hidden>
- Date: Fri, 17 Mar 2006 09:22:07 -0500
On Mar 16, 2006, at 8:41 PM, Chuck Hill wrote:
On Mar 16, 2006, at 5:34 PM, Art Isbell wrote:
On Mar 16, 2006, at 3:24 PM, Mohapatra Ashish wrote:
I am back again. This time with a question of where to draw line on
horizontal scaling and go for application threading.
All WO apps are multithreaded, so you probably intend to enable
concurrent request handling.
Are there any more issues sighted on this than the effort of
making complete
thread-safe application.
A potential problem with trying to increase performance by using
concurrent request handling is that database access remains single-
threaded. So if your app accesses a database frequently or some
accesses are slow, using concurrent request handling may not
provide as big a performance gain as increasing the number of
instances.
I'll simply add that you should always enable concurrent request
handling unless your code has defects in it that prevent you from
enabling it. While it may not be as big a gain as more instances,
it is still a gain.
I believe there is one important exception to this rule. Java client
applications don't seem to work properly with concurrent request
handling. I believe the object distribution layer requires
sequential request handling.
Robert Walker
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden