Background
In order for you to work smoothly with timeSensor LEGAL, you need a fast and reliable Internet connection. If the server is on the same network as its workstation, i.e. in the local network (LAN), this is no problem. However, if the server is elsewhere, you should check that your connection to the server is sufficiently fast.
Latency vs. Bandwidth
Internet connections are usually sold via up- and download information. This information concerns theBandwidth, i.e. the capacity of data transmission when uploading and downloading data. If you take the analogy to a water pipe, the bandwidth represents the diameter of the tube: the larger the diameter, the higher data volume can be transmitted at the same time. bandwidth is usually sufficient: choose a connection here with200 Mbit/s or better, then large documents are downloaded quickly.
The speed at which the data packets travel back and forth between your workstation and the server is calledLatency. To stick to the image of the water pipe: latency is a measure of flow speed. If the tube is very thick, but the water flows very slowly, so little water still comes out. Latency is often swept under the carpet by Internet providers, as it is difficult to ensure it. The reason for this is that data packets are passed on via routers and switches (so-called "hops") in a way that is poorly predictable. Fortunately, you can measure latency quite easily.
How to measure latency?
The PING command is available to measure latency. Call on WindowsCmdthe command prompt, or call theTerminalWindowson. Now enter the commandPingwith a destination address. The destination address can be either an IP address or a DNS name. For example, to measure speed to Google, type:Ping 8.8.8.8and press Enter. Now the system sends a number of data packets to the Google Server and shows how long it took for the data package to be returned.
Here you can see a table with different destination addresses and the expected PING times for Switzerland:
Target | Command | Optimal | Ok | Slowly |
Google | Ping 8.8.8.8 | < 10ms | 10-15 ms
| > 20ms |
Flow Swiss (CH) | Ping185.90.37.202 | < 10ms
| 10-15 ms
| > 20ms |
Meta 10 (CH) | Ping62.121.225.32 | < 10ms
| 10-15 ms
| > 20ms |
Infomaniak (CH) | Ping 195.15.218.134 | < 10ms | 10-15 ms | > 20ms |
Strato (EN) | Ping 185.90.37.201 | < 10ms | 10-15 ms | > 20ms |
This is what it looks like on macOS when measuring latencies (here to Flow Swiss):
On Windows, the window looks slightly different, but works identically in principle:
What to do if latency is too slow?
Check different goals: if the PING times are slow everywhere, you should contact your Internet provider and inquire about a fiber optic connection. If the PING is slow only to one provider, you should possibly use the server. with another provider. Finally, you can of course also run the database server classically in the firm. The latency for access to a local database server is fantastic, just under 1 ms.
Wi-Fi - No thanks!
A large "latency eater" is Wi-Fi. If you run a professional database application such as timeSensor LEGAL, you should not connect your computer to the Internet via Wi-Fi. WLAN increases latency and is comparatively unstable. Always connect your workplace via a real network cable to enjoy the optimal speed and stability.
Are there alternatives?
A good alternative to poor or unstable latencies is the operation of servers and workplaces in the data center. With this approach, also known as virtualization, latencies are as good as with a locally operated database server (i.e. below 1 ms) because servers and workstations are operated in the same data center. Virtualized workstations usually run under the Windows operating system. There are a large number of providers that offer virtualization solutions,
for example here.