Interface Multilink Vs Interface Virtual Template

Multilink PPP (MLP) balances load over dialer interfaces, such as ISDN, synchronous, and asynchronous interfaces. MLP splits packets and sends the fragments over parallel circuits. This way, MLP improves throughput and reduces latency between systems. MLP provides a method to split, recombine, and sequence datagrams across multiple logical data links. MLP allows packets to fragment, and the fragments to be sent at the same time over multiple point-to-point links to the same remote address.

virtual template interface are used to combine multiple interfaces in to one virtual interface called virtual template.

for detailes ps check the following link:
https://www.cisco.com/c/en/us/support/docs/wan/point-to-point-protocol-ppp/10379-mpp-serial.html

all the best

jskfan

Here is your answer in this thread:
https://community.cisco.com/t5/routing/multilink-virtual-template/td-p/1397195

"Interface Virtual-Templates are intended for dynamic access, in other words - dial-in and dial-out features from/to the router.

It is also use on PPP over Frame-Relay configurations as the command frame-relay interface-dlci xx ppp calls for a virtual-template to clone from, not a multilink interface. You can still use the multilink interface along with the virtual-template by binding the multilink with same ppp multilink group.

Another benefit of using a Virtual-Template that when the Virtual-Access is not in use, those resources are freed up by the router.

While, if you use Interface Multilink, those resources will be allocated permanently until you delete the interface from the config.

In terms of usability, they both offer the same kind of services and features under the logical interfaces.

All commands applied under the Interface Virtual-Template are valid under the Interface Multilink."