KSE system scope vs non system scope threads

[David Xu]

Christopher M. Sedore wrote:

>I'm using blocking connects.  Degradation is I should be moving ~5-7MB/sec (and I do if I don't try to connect to any hosts that are down).  Once I do, I see fluctuations from ~15-20KB/sec (note: KB) to 3-5MB/sec, somewhat associated with when the connects happen.  Running libthr, I move 6-7MB/sec consistently (until everything hangs up showing sigwait as the status in top, anyway).  System scope threads turn in numbers from 5-6MB/sec.  (Note I don't have any hang problems under KSE, only libthr.)
> 
>On Monday I'm going to try David Xu's suggestion of trying v1.18 of thr_spinlock.c to see if that helps.
>
>  
>
I don't know if you hit a hard limit in kernel. The hard limit is
sysctl kern.threads.max_threads_per_proc, default is 150, it means
system only allows 150 threads to be blocked in kernel, if you hit the
limits, then performance will be degraded.

David Xu

>-Chris
>_______________________________________________
>freebsd-threads at freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-threads
>To unsubscribe, send any mail to "freebsd-threads-unsubscribe at freebsd.org"
>
>  
>