I suppose this is a feature suggestion. MBuffer has a almost miraculous impact on the performance of zfs send/receive in my environment, whether on a low latency local gigabit connection or a high latency low bandwidth vpn connection going site-to-site. For the times when it really matters I get the data moved in a hurry, on a secure network I usually do the following:
source: zfs send | compression of some sort | mbuffer
destination: mbuffer | uncompress | zfs receive
There could be an ssh step in here if I was concerned about the security of the network. It's rare with this combination (picking the correct compression so as not to be cpu limited) I can't saturate a link.
If I'm not missing some deal breaking reason, it would be great to have an mbuffer option in the GUI replication tab.
source: zfs send | compression of some sort | mbuffer
destination: mbuffer | uncompress | zfs receive
There could be an ssh step in here if I was concerned about the security of the network. It's rare with this combination (picking the correct compression so as not to be cpu limited) I can't saturate a link.
If I'm not missing some deal breaking reason, it would be great to have an mbuffer option in the GUI replication tab.
