Hi, > The main problems is when the user submits to a PHP script looking for > data...
Exactly there you should start looking for the problem ... > there are several secs of a delay before any data is returned (on a local > network accessing SAP DB on Linux, using SAPs ODBC )... > > This happens each and everytime the script is executed... With DB pooling we > hoped that there would be no wait getting a connection (as there would be > one available in the pool) and the data would be replied quicker. On > subsequent requests for data replies would also be quicker. > > Will DB pooling resolve this? Hm. When I developed an apache module in c++, I thought it is necessary to open the connection to sap db when the apache forks the child at startup, and release the connection only when the server terminates. (With apache modules, the process is persistent). But I discarded this, and now I open and close a connection for every request, because it is so fast. Typically I have execution-times of 0.01 to 0.1 seconds per request on a i386 1GHz, including xml-parsing, database-operations etc. To me it looks like sap db caches the connections. Does anybody know if this is true? Regards - axel _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
