4 ms·

Is t the same for resources used on the client side, on mobile in particular?

• jwsi 6y ago
  Our mobile apps are lightweight in terms of resource utilisation. This is largely due to two factors: 1) We utilise low level pause and resume network calls provided by the operating system such that the VPN is only active when network data is being sent or received. Therefore, when a device is on standby, the VPN is paused preventing battery drain and resumed whenever the device polls for notifications or is awoken. 2) Most OpenVPN implementations on iOS/Android (e.g. https://github.com/ss-abramchuk/OpenVPNAdapter https://github.com/ss-abramchuk/OpenVPNAdapter) utilise socket bridges, this has the effect of increasing the resource utilisation massively for a given throughput as you have to copy data to and from the network socket when sending or receiving data. Our VPN core writes and reads directly from the underlying tunnel socket which reduces resource utilisation heavily. Both of these optimisations make our mobile applications very efficient. If you try it out and run into issues, we also have a very active docs hub where people ask questions and request features (https://github.com/ultrahorizon/UH-VPN-Docs https://github.com/ultrahorizon/UH-VPN-Docs).