×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
From: Aaron Bartell
I would be curious to know how much CPU time is required to
create a new J2EE thread vs. have Apache hand-off a "CGI" request to
an existing job?
You're probably dealing in microseconds either way; less than 1 millisecond.
But how often do JEE application servers create new threads? The IBM i HTTP
server appears to reuse threads activated at startup. Do JEE servers create a
new thread for each request? Like they create new "request" and "response"
objects for each request?
Actually, they say that JEE servers only create one instance of each Servlet.
Servlet methods may be called by each thread. That would be quite a bit
different than CGI, where you might have an instance of each *PGM loaded in each
CGI worker process.
JEE app servers evidently synchronize Servlet method calls. Servlet methods can
easily get quite complex. That's probably why JEE app servers DON'T scale well.
Okay, I said it. IMHO, they don't scale well. Studies show that JEE application
servers don't have the ability to effectively utilize multiple processors,
unless you launch multiple instances, and deploy applications under each.
Contrast that with CGI worker jobs that effectively utilize all processors.
-Nathan
midrange.com
