When you use PDM and are working remotely or have multiple sites you can run into two issues that can cause performance concerns, latency and packet loss.
The following is a general guideline for Latency when working with PDM.
- Ideal latency between a PDM client computer and the Archive server is under 50ms.
Ideal is where you will see the best performance for your PDM client.
- Good latency is 50-100 ms.
This means you may see some performance issues, but they will be minor, such as taking 10-15 seconds to check a file in rather than 3 that may be seen with an ideal latency.
- Not-good but still usable latency is 100-150ms.
This is the latency that means you will see performance degradation and delays in PDM actions. For example, check in may now be 45-60 seconds where it was only 3 on an ideal connection.
- Bad latency is 150-200ms.
This is the latency that may still work, but is going to have extreme performance degradation, timeout errors and connection failures. For example, check in may now be 90-120 seconds where it was only 3 on an ideal connection or may even fail to check in with a timeout error periodically.
- Unusable latency is over 200ms.
Theoretically your client may connect to the Archive and you may be able to complete a PDM action but this level of latency is considered unusable when SOLIDWORKS tests PDM Performance issues.
The following is a way to test for packet loss and comes from the SOLIDWORKS KB S-059810.
Running this test for 5-10 minutes can give enough data points to know your general packet loss statistics. The larger the packet size you can use for this test, the more the results will be representative of the packet loss PDM will experience.
- Ideal packet loss is under 0.1%
- Packet loss over 0.1% but under 1% is still good.
- Packet loss between 1-5% is not good; you may still be able to use this connection but expect timeouts and errors.
- Packet loss between 5-10% is bad and may lead to file corruption as packets fail to update the archives.
- Packet loss over 10% is unusable for PDM.
S-059810 – Is there a test to determine if a network connection to a machine is continuous and uninterrupted?
One method is to use a PING test that writes to a text file. You can run this for a period of time to test connectivity during the duration of the test. Pressing CTRL-C will end the test.
ping [server] -t -l 1500 >> c:pingtest.txt
- [server] should be the name of the machine you are testing the connection to. The brackets should be removed when writing in the real machine name. You can also use IP address, especially if DNS is not functioning properly.
- 1500 is the packet size. This is a very large packet and may be lowered in size if PING testing affects network performance.
- >> Is a switch that means APPEND to the following file. Using a single bracket > would mean overwrite file.
- C:pingtest.txt is the file that is created that will contain the PING results. Make sure the user has rights to create a file in this folder. If they do not they can choose to create the file in another folder by simply modifying this path.
- Connectivity errors will display as ‘Request timed out.’ within the text file.