OO4O/IIS/global connection pool

Hi...

        I'm load testing a web page using OO4O 8.1.7 to get records back from an Oracle database and print them on a page. I've found that the OO4O IIS examples all use the connection pool at global scope and i've also found that as you put load on the page, performance degrades seriously even in the most inane of places.

        Once you get a connection out of the connection pool and execute your query, it starts taking inordinately long even to get a column out of the Dynaset. It's like there's some kind of contention even though the dynaset is local to a single instance of the page.

        As a test, i stopped using the global connection pool and had each page connect directly. I found that the processing of the result set got much quicker, though extra time was burnt building and tearing down connections all the time. The result was overall throughput improvement of about 50% *NOT* using the connection pool.

        does this strike any cords with anyone? is there a way to get connection pools to work without engendering a lot of synchronization overhead (or whatever is bogging it down)?

        I tried using the Oracle Provider for OLE and it was generally much quicker but it leaked memory like a sieve accessing CLOBs and can't be used...

thanks
-mark Received on Wed May 09 2001 - 00:53:32 CEST