RE: CGIDEV2 performance versus Net.Data

I like the Queue method.  The web server call a CGI program that forwards
the transaction to a data queue.  The web pages hold the qlib/qname to send
to.  The data sent to the queue hold the session ID.  The response is sent
back to a second standard queue with the session ID as the key.  The CGI
program, after sending the data, waits at this queue for the keyed response.
The CGI program needs to read just three pieces of data from the page, Queue
Lib, Queue Name, and Session ID.  The same program can be used for all web
pages.  Now we have data queue server jobs running in a dedicated subsystem
with dedicated resources for processing the transactions.

We found that with our authorization application, we can process 200
transactions a minute on our 720/2062 with interactive of 120 and total of
420.  This is a heavily loaded system and I am running the transaction from
a single threaded batch job.  That is: read a record, send to queue, wait
for reply, update trans, and like shampoo instruction, repeat.  Our
authorization application has dozens of files open.  Now on our old model
400/2131 can process about 80/minute.  This system is dedicated to our
transaction processing.

This is very scalable.  All you need to do is start up more instances of the
data queue server.  We actually do that dynamically by looking at the
timestamp of when the transaction was placed on the queue to when it was
pulled off.  If more than xx seconds, submit another copy up to the defined
maximum number of server instances.

Christopher K. Bipes      mailto:ChrisB@Cross-Check.com
Operations & Network Mgr  mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.                  http://www.cross-check.com
6119 State Farm Drive     Phone: 707 586-0551 x 1102
Rohnert Park CA  94928    Fax: 707 586-1884

-----Original Message-----
From: Goodbar, Loyd (AFS-Water Valley) [mailto:LGoodbar@afs.bwauto.com]
Sent: Friday, October 05, 2001 8:35 AM
To: 'midrange-l@midrange.com'
Subject: RE: CGIDEV2 performance versus Net.Data


These are neat ideas, especially the socket server. But I don't understand
how a socket server improves performance, I can't picture the
architecture...

Traditional CGI:

1. web browser request is sent to
2. http server, which calls
3. custom CGI program, which generates output back to
4. HTTP server, which sends the page to
5. web browser