Re: Message Server Plug-In

>I wonder if the performance issues change with persistent CGI?

I don't have any real-world persistent CGI examples to compare to.  It
should definately reduce CPU consumption.  But the problem I see with
persistent CGI is the one to one correlation between end-user and server.
The server remains active, but only for one user.  If you have 1000 active
users, then you need 1000 active servers.  If you have 1000 users needing 10
applications, then you need 10,000 active servers.

There's the question about how long a CGI server instance should remain
active, and dedicated to a single session, and how to terminate it?  Also,
when and how to call RCLACTGRP to free the resources of the entire
activation group?

I've never used persistent CGI, so maybe somebody can answers these
concerns.

With a message server in the middle, if an avarage user submits a new
request every 10 seconds, and it takes the application server 10msec to
handle that request, then a single instance of a single application server
can handle 1000 concurrent users.

Nathan.


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---