1678 Network issues: Performance on network

VERSIONS: Paradox 7 and later, Win 2000, Win XP, and later
SUBJECT: Slow performance when opening form with tables on network
BY: G. RAMBALDI - RAMBALDI SISTEMI
Date: 4 April 2004

I have discovered that Paradox runs very slowly when a form containing tables is opened, at the same time as an 'Explorer' window is opened on any folder on the same server that contains the Paradox tables and forms!

In Win 2000 the registry value is TcpDelAckTicks ( =0)

In Win XP & Server 2003, the registry value is TcpAckFrequency (=1). This value works for me.

As the Registry value in this case is rather complex, you have to read the The Microsoft Knowledge Base article mentioned by Luc Kumps, (see below) to get the full details on where to find this setting.

Document is titled: Slow performance occurs when you copy data to a TCP server by using a Windows Sockets API program

For details, see KB article 823764.


VERSIONS: All
SUBJECT: Performance on network
BY: LUC KUMPS
Date: 25 February 2004

I wanted to test the performance of our new forms over a network, and so I installed my data tables on my portable (XP Home), which would play 'server'. My Win2K desktop would be 'client'.

Simply opening any form took somewhere between 30 and 45 seconds.

Searching for "paradox network performance open form" revealed that a lot of other people had been struggling with this in the past, but they were only offered some advice on keeping a TCursor opened, using indexes, setrange, etc. This didn't apply to our forms. So I decided to monitor the network traffic, and noticed very regularly a 200ms delay before a TCP/IP ACK was sent out from the client to the server. This delay is caused by the registry parameter TcpDelAckTicks.

After I defined this key (setting the value to 0), and after rebooting the system, the "open form" delays where TEN TIMES lower: between 3 and 4 seconds!!!

For details, see KB article 321098
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q321098
The KB article "applies to" server systems. But in the case of Paradox on a network, it is clearly applicable to 'client' systems as well!!!

If your Paradox form is starting up REALLY slowly on a network, give it a try!


VERSIONS: All
SUBJECT: Performance on network
BY: KIM A. HOWARTER
Date: 07 February 2003

I also had a problem at my work location with slow file access in Paradox 9 sp4. We fixed it by changing a setting on the network card.

Specifically the change was: change the "Link Speed & Duplex" setting from "Auto" to "100Mbps/Full Duplex".

This was done yesterday morning. So far, it has worked to speed up my form access and switching from design to run mode improved from 15 to 20 seconds to 1 to 3 seconds. Evidently, the network adaptor was not connecting at the faster speed when allowed to do it automatically. By forcing it to 100Mbps/Full Duplex, it gave me faster access according to our network consultant.

To index