Kbase P98650: Poor performance with 4GL session connected in client server although a shared memory connection cou
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/12/2004 |
|
Status: Unverified
SYMPTOM(s):
Poor performance
4GL batch job running on same machine as the database server machine
4GL session running on the database server machine
CAUSE:
Using remote connection to the database with the -S connection parameter. This is also called a "Client Server" connection although everything takes place on the same machine, and the client is also called a "Remote Client".
Examples:
-db myDatabase -S myTcpPort
-db myDatabase -S myTcpPort -H localhost -N TCP
Such a connection involves the TCP local loop (also call TCP loopback) and involves a remote server process (_proserve.exe), which leads to lot of unnecessary overhead.
FIX:
Use a shared memory connection by specifying the full path into the -db parameter, and not using the -S , -H and -N parameters. This type of connection is also called a "direct connection", and the client a "direct client" or "self client".
Examples:
-db /usr/db/myDatabase.db
-db C:\MyDbDir\myDatabase.db
One may have a huge performance gain like 200% or 500% or even 1000% depending on the application, because the client accesses the databases directly without involving an unnecessary remote server.