Re: Which scales better? J2EE, PHP, or CGIDEV2?

["Dean, Robert" <rdean@xxxxxxxxxxxx>]

Yes they do.  Some of the app servers (Jetty for sure) also manage connections the same way i manages jobs (i.e., requests that are waiting for backend I/O are shuffled off to a separate pool and the sockets are reused for other requests).  This allows concurrent requests to scale beyond the number of TCP/IP ports available.

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Nathan Andelin
Sent: Thursday, October 07, 2010 12:44 PM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Which scales better? J2EE, PHP, or CGIDEV2?

> From: Aaron Bartell
> I would be curious to know how much CPU time is required to
> create a new J2EE thread ...


I answered hastily the last time.  Instantiating a Thread in Java is trivial, 
but depending on what else may be instantiated from within a Thread, it could 
get expensive.  I don't know what might get instantiated from within JEE server 
threads.  But it would make a lot more sense to reuse a pool of threads for 
incoming browser requests, which is what app servers do, according to Thor.  So 
the question is probably moot.

-Nathan