I had exactly the same behaviour with apache/php/iodbc/sapdb (3 seconds
delay).
The strange solution was, to create a unix user "sapdb" on the web
server(SuSE machine)???
I can't imaging why...

regards,
Kolja


-----Urspr�ngliche Nachricht-----
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Auftrag von Koetter,
Thomas Theodor
Gesendet: Donnerstag, 10. Juli 2003 09:40
An: 'Latonio, Jason H'; [EMAIL PROTECTED]
Betreff: RE: sapdb, apache, php odbc_pconnect


Hi Jason,

> -----Original Message-----
> From: Latonio, Jason H [mailto:[EMAIL PROTECTED]
> Sent: Dienstag, 8. Juli 2003 14:57
> To: [EMAIL PROTECTED]
> Subject: sapdb, apache, php odbc_pconnect
>
>
> i am using apache 1.3.26
> sapdb 7.3
> and php using odbc_pconnect to interface php with sapdb.
>
> before i was using odbc_connect to interface with sapdb, but
> the performance was unacceptable, each page that called the
> DB was delayed for about 3 secs, which got very annoying.
> so i thought the problem was i that i wasn't using persistent
> connections, so i did the following:

Unfortunately I don't know PHP's ODBC really in detail, but
the delay of 3 sec for a connection sounds a little bit long.

Please, could you check, whether

 - a connect over PHP (without Apache etc) takes also as long.
 - a small ODBC program needs also 3 sec.


I assume, the time is lost somewhere else but not in the
connect (if the machine is not continously swapping).
In the mailling list archive problems are reported due to
name resolving. Could you check that, too (i.e. instead of
the host name use the IP-address)?


With kind regards  Thomas


----------------------------------------------
Dr. Thomas K�tter
SAP DB, SAP Labs Berlin


Hurry up, SAP DB is open source     www.sapdb.org



_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general


_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general

Reply via email to