Re: kern.maxswzone causing serious problems

2018-04-10 Thread Curtis Villamizar
Replying to myself... again. Bug report https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227436 has been submitted. Hopefully this can get picked up in 11.2 and maybe patched into 11.1. If not at least go into 12. Curtis In message <387a65b7-d221-0a10-b801-1dd573054...@orleans.occnc.com>

Found the issue! - SCHED_ULE+PREEMPTION is the problem

2018-04-10 Thread Peter
Results: 1. The tdq_ridx pointer The perceived slow advance (of the tdq_ridx pointer into the circular array) is correct behaviour. McKusick writes: The pointer is advanced once per system tick, although it may not advance on a tick until the currently selected queue is empty. Since each

Re: more data: SCHED_ULE+PREEMPTION is the problem

2018-04-10 Thread Peter
Hi Stefan, I'm glad to see You're thinking along similar paths as I did. But let me fist answer Your question straight away, and sort out the remainder afterwards. > I'd be interested in your results with preempt_thresh set to a value > of e.g.190. There is no difference. Any value above 7

Appendices - more data: SCHED_ULE+PREEMPTION is the problem

2018-04-10 Thread Peter
I forgot to attach the commands used to create the logs - they are ugly anyway: [1] dtrace -q -n '::sched_choose:return { @[((struct thread *)arg1)->td_proc->p_pid, stringof(((struct thread *)arg1)->td_proc->p_comm), timestamp] = count(); } tick-1s { exit(0); }' | sort -nk 3 | awk '$1 > 27