Make the remoting pipeline on the node throttle data sent to or received from the given remote peer. Throttling works by delaying packet submission within the netty pipeline until the packet would have been completely sent according to the given rate, the previous packet completion and the current packet length. In case of large packets they are split up if the calculated end pause would exceed `akka.testconductor.packet-split-threshold` (roughly). All of this uses the system’s scheduler, which is not terribly precise and will execute tasks later than they are schedule (even on average), but that is countered by using the actual execution time for determining how much to send, leading to the correct output rate, but with increased latency. ====Note==== To use this feature you must activate the failure injector and throttler transport adapters by specifying `testTransport(on = true)` in your MultiNodeConfig.

public Task<Done> Throttle(
	RoleName node,
	RoleName target,
	ThrottleTransportAdapterDirection direction,
	float rateMBit
)

member Throttle : 
        node : RoleName * 
        target : RoleName * 
        direction : ThrottleTransportAdapterDirection * 
        rateMBit : float32 -> Task<Done>