Seems like I am confusing you I do realize that it is in BITS!
4M == 4000KBIT == 500kbytes. Using 4000K OR 4M SHOULD restrict flow to a MAXIMUM of 500 KBYTES. What I am seeing is that using a value restricts flow to a maximum of 100KBYTES! root@storage1:/root# flowadm add-flow -l backup0 -a transport=tcp tcpflow root@storage1:/root# flowadm set-flowprop -p maxbw=4M tcpflow ubuntu-16.04.1-desk 0%[ ] 2.67M 104KB/s eta 3h 45m # Well gosh darnit. That doesn't make sense. Maybe his adapter cant download more than 100KBYTES. Lets undo what we did and see what happens. root@storage1:/root# flowadm remove-flow -l backup0 desktop-amd64.iso?_ 1%[ ] 18.24M 1.00MB/s eta 85m 54s # It appears our download speed is running at 8 MEGABIT or 1MEGABYTE without any flow. So why would a restriction of half of our download rate cause it to run at 1/10th the maximum speed! On Wed, Jan 11, 2017 at 8:52 PM, Dan McDonald <dan...@omniti.com> wrote: > > > On Jan 11, 2017, at 8:32 PM, Mini Trader <miniflowtra...@gmail.com> > wrote: > > > > This does not work. Simple example. Ran wget on an ubuntu ISO. Was > downloading at over 1 mega byte per sec. Set adapter to 4000K. I would > expect the download to peak at around 500 Kilo Bytes. Was in the 100 > range. 16000K put it in the 500kb range. Doesn't add up. Also didn't > persist across reboot of zone. > > 1.) flowadm works in units of bits/sec, not bytes. 4000kbit == 4mbit == > 500kbytes. Please RTFM carefully. > > 2.) Use it in the global zone for the NIC you're assigning. Then it'll > persist. Persistence of /native commands in LX zones is an open problem > right now. We aren't planning on doing it for flowadm, only for ipadm. > > Dan > > > >
_______________________________________________ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss