Re: Improving CGI/ODBC/Oracle8 Performance

Roy Smith wrote in message ...
>Sean Black <zoot_at_mcs.net> wrote:
>> It appears that the vast majority
>> of that time is spent in making the connection from the application to
>> Oracle8--once connected, the queries seem to execute very quickly.
 <snip>
>The obvious answer is some sort of persitant intermediary process, which
>connects once to the database and hangs around waiting to serve CGI
>requests.

Why not try the ISAPI (Microsoft's Internet Server API) or NSAPI (Netscape Server API)? ISAPI (not so sure about NSAPI on Unix) is a DLL on NT that is dynamically loaded by the web server. When this DLL is loaded, it can connect to Oracle and multi-thread web browse "CGI" requests afterwards on this connection. I suggest going to the Netscape or Microsoft web sites for more info on how these APIs work.

Another reason why connects may seem so slow, is the time it takes to load all the DLLs into memory for a client server connection. When using Oracle over ODBC, several DLLs are required and must be loaded by Windows. If that application or CGI terminates and the internal usage count of these DLLs drop to zero, Windows auto unloads them to free up memory. So the next time the CGI runs the DLLs are loaded all over again.

A simple trick may be to write a little app that simply dynamically loads these DLLs at boot time so that they are there ready in memory when the CGI runs.

regards,
Billy Received on Tue Jan 13 1998 - 00:00:00 CST