CURRENT slow and shaky network stability
O. Hartmann
ohartman at zedat.fu-berlin.de
Sat Mar 26 19:01:32 UTC 2016
Am Sat, 26 Mar 2016 13:28:16 -0400
Michael Butler <imb at protected-networks.net> schrieb:
> -current is not great for interactive use at all. The strategy of
> pre-emptively dropping idle processes to swap is hurting .. big time.
What is the gain then?
If this "feature" results in corrupted ssh sessions, slow console sessions or even worse:
prolongued compilation times, then it is a big fail!
>
> Compare inactive memory to swap in this example ..
>
> 110 processes: 1 running, 108 sleeping, 1 zombie
> CPU: 1.2% user, 0.0% nice, 4.3% system, 0.0% interrupt, 94.5% idle
> Mem: 474M Active, 1609M Inact, 764M Wired, 281M Buf, 119M Free
> Swap: 4096M Total, 917M Used, 3178M Free, 22% Inuse
>
> PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU
> COMMAND
> 1819 imb 1 28 0 213M 11284K select 1 147:44 5.97%
> gkrellm
> 59238 imb 43 20 0 980M 424M select 0 10:07 1.92%
> firefox
>
> .. it shouldn't start randomly swapping out processes because they're
> used infrequently when there's more than enough RAM to spare ..
>
> It also shows up when trying to reboot .. on all of my gear, 90 seconds
> of "fail-safe" time-out is no longer enough when a good proportion of
> daemons have been dropped onto swap and must be brought back in to flush
> their data segments :-(
>
> Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-current/attachments/20160326/01374f23/attachment.sig>
More information about the freebsd-current
mailing list