Re: Direct Connect vs. Web Server
Re: Direct Connect vs. Web Server
- Subject: Re: Direct Connect vs. Web Server
- From: Karl Gretton <email@hidden>
- Date: Tue, 06 Jan 2004 10:07:28 -0500
If you are running using either JSP/Servlet or true WAR deployment
within an AppServer (such as JBoss or SilverStream) then there isn't a
web server involved in the process. It can make a significant
difference to the performance of the application when there are large
transfers taking place such as graphics or video.
In addition, I believe that Robert is incorrect; each and every request
goes through the web-server and not directly to the WO server when
using a web-server and adaptor. The first request consults WOtaskd to
perform load balancing etc. Subsequent requests are still proxied by
the adaptor so there is always the communications overhead. Indeed,
there doesn't even need to be a valid route from the WO server to the
outside world - a useful security feature in some scenarios.
Karl
On Jan 6, 2004, at 12:33 AM, Robert Walker wrote:
If my understanding of direct connect mode serves, you would be
bypassing the adaptor altogether. The adaptor is responsible for
handling load balancing and finding the appropriate instance for the
initial request. I guess you might get a performance boost for the
first request from the user. Subsequent requests are directed back to
the same instance directly as in direct connect mode.
I would also think you would have firewall issues, since you would be
connecting directly to the port where the instance is running instead
of through port 80. Maybe you would get a performance boost by
connecting directly to the port. However, if your instance is running
on port 2005 it is probably blocked by the firewall. Normally you
want to limit web traffic to port 80 (or 443 for SSL).
I very well could be wrong about this, but I don't see any real
benefit of using direct connect for performance reasons (testing and
debugging yes). It seems to me that you would have other problems on
a high traffic site that has multiple instances and multiple
application servers, unless you're doing some really tricky stuff to
support your own load balancing scheme for direct connect.
Like I said, I may be misunderstanding direct connect, so maybe
someone can shed more light on this mystery.
On Jan 5, 2004, at 10:43 PM, King Chung Huang wrote:
In the thread, "Advice on dynamic graphics with WO", Karl mentioned
running apps in direct connect mode, bypassing the web server. In
general, does anyone know beneficial this is? Is it small enough that
only very heavy loads would benefit, or is there an appreciable
difference even for small loads? I've never really thought about it
and that comment caught my eye.
King Chung Huang
Learning Commons
University of Calgary
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
--
Sincerely,
Robert Walker
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.