When looking for the cause of performance issues, the database network
interplay should be considered, too.
When starting ClassiX® (as
an ObjectStore client) it is necessary to resolve the client IP address again as
a client name.
If the start phase takes unusually long, this could be a problem.
With
ping -a <die IP-Adresse des Clients>
on the server, it should be double-checked how long the reverse lookup will take.
By entering the own name+IP address into the server file
WININT\SYSTEM32\DRIVERS\ETC\hosts
it is possible to achieve an acceleration.
set OS_DEBUG_NETWORK=1
set OS_STDOUT_FILE=fileName
the file shown above, will provide information about ObjectStore network activities.
Microsoft Windows© supports several network cards with which a PC can connect to the network. If there is a Windows© network request by the software, Windows© tries to pass its internal priority to one network card after the other.
Windows© waits for a response after each transfer. If there is no response - for example because no network cable is connected to the according network card - Windows© waits up to the defined network timeout and tries the next one.
There are the following possibilities to change network card priorities:
It is now possible to define the network card order via arrow up/down. Here, the default network card should always be at the very top.
It can help to finally remove network cards, which have only been taken out of the system without removing the entries in the device manager. First of all, all devices that have been hidden because they are not active/part of the system need to be displayed in the device manager. These devices are marked with a red x and can be removed via context menu:
