Point-to-site. PTS for now on. PTS is a way of connecting single clients (machines) to a gateway in Azure, without connecting the entire infrastructure to it. In this case, you only need a client computer, instead of an enterprise router. The client machine connects directly to Azure via VPN.
Will this be faster that Azure Site-to-Site?
Test #5 10kb message
10Kb is our base message. PTS didn’t show any issues regarding this one.
Execution time is practically the same as before (on Site-to-Site scenario), with the same message size. 1% is not noticeable on a large batch execution. Let’s see for 100KB. If results change more drastically, then we can analyze and find a reason for this.
Test #5 100kb message
We didn’t see a big difference before. Will 100kb be the game changer?
Actually, it is! It’s ~10ms faster than before! Site-to-Site is beginning to lose to PTS.
Probable causes are:
- Router delays due to packet queues (Site-to-Site)
- Router processing power limitations of encrypting packets (and routing them)
- General hardware limitations
We start to see some differences now. ~10ms is a noticable improvement. How fast will 5MB be?
Test #5 5mb message
The ultimate test on PTS.
Well, PTS it’s not for large messages. It’s inefficient and takes a lot of time! You should only use this for a one-time-only scenario, like accessing a VM or downloading some files from Azure. Processing large messages with PTS is not recommended, as execution times increased ~1 second in average.
Overall test discussion
This is an awkward situation. 100KB is faster than Site-to-Site, but 5MB it’s not. While processing small to medium messages you should be fine. Not recommended for production as it showed to have some unusual peaks, so latency may be compromised.
Go to next test!
