TurboDB Engine Documentation

Network Throughput and Latency

Previous  Top  Next

The network performance is critical for the performance of your TurboDB applications especially, when it is used in multi-user mode. Network problems are the most frequent reason for poor database throughput and should therefore checked out first in case of performance problems. You might have a network problem, if the computer with the database files is different from the one with the application and your application is generally very slow or gets generally very slow, as soon as a second database client is started.

Because network problems are sometimes hard to detect, dataweb offers a free program, which measures network operations typical for databases called NetTest. You can download this program from our Web site or request it from the dataweb support. This test program will enable you to determine within five minutes, whether the network is the cause of a performance problem or not.

In case the network turns out to be slow, there are different points to check out:

Check whether some virus checker or other software is conflicting with TurboDB files. These programs tend to check these highly dynamic files after each modification and thereby slow down or even completely block the database access. You can safely configure the virus checker to not check TurboDB files, because they are not executable.
Check whether there is updated driver software for your network adapter or if it is defect.
There is a known problem with SMB signing, if you access a Windows 2000 domain controller from Windows XP clients. Please refer to Microsoft knowledge base article 321098 for more information and the resolution.
Hubs between database clients and the database file server sometimes block access, if the network traffic is too high. In this case they should be replaced by a good switch.