Bad
root@storage1:/root# dtrace -s tcp_tput.d
^C
unacked(bytes) 10.250.0.3
2049
value - Distribution - count
32 | 0
64 |@@@
Running the following dtrace.
#!/usr/sbin/dtrace -s
#pragma D option quiet
tcp:::send
/ (args[4]->tcp_flags & (TH_SYN|TH_RST|TH_FIN)) == 0 /
{
@unacked["unacked(bytes)", args[2]->ip_daddr, args[4]->tcp_sport] =
quantize(args[3]->tcps_snxt - args[3]->tcps_suna);
}
tcp:::recei
If it helps. This doesn't happen on NFS from the exact same client. How
do I file a bug?
On Tue, Mar 8, 2016 at 1:51 PM, Mini Trader
wrote:
> Simple example.
>
> 1 Server 1 client.
>
> Restart service everything is fast. A few hours later from same client
> (nothing happening concurrently) sp
Simple example.
1 Server 1 client.
Restart service everything is fast. A few hours later from same client
(nothing happening concurrently) speed is slow. Restart service again,
speed is fast.
Its like CIFS starts off fast than somehow for whatever reason if it is not
used, the connection for m
8 марта 2016 г. 6:42:13 CET, Mini Trader пишет:
>Is it possible that CIFS will ignore TCP buffer settings after a while?
>
>I've confirmed my systems max transfer rate using iperf and have tuned
>my
>buffers accordingly. For whatever reason CIFS seems to forget these
>settings after a while as spe
Is it possible that CIFS will ignore TCP buffer settings after a while?
I've confirmed my systems max transfer rate using iperf and have tuned my
buffers accordingly. For whatever reason CIFS seems to forget these
settings after a while as speed drops significantly. Issuing a restart of
the servic
