Date: Sun, 30 Nov 2003 20:17:22 -0500 From: "Christopher M. Sedore" <cmsedore@maxwell.syr.edu> To: "David Xu" <davidxu@freebsd.org> Cc: threads@freebsd.org Subject: RE: KSE system scope vs non system scope threads Message-ID: <32A8B2CB12BFC84D8D11D872C787AA9A02B1F790@EXCHANGE.forest.maxwell.syr.edu>
index | next in thread | raw e-mail
I don't presently have more than 20-30 threads running at any one time. -Chris ________________________________ From: David Xu [mailto:davidxu@freebsd.org] Sent: Sun 11/30/2003 6:25 PM To: Christopher M. Sedore Cc: deischen@freebsd.org; threads@freebsd.org Subject: Re: KSE system scope vs non system scope threads 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@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-threads >To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd.org" > > >help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?32A8B2CB12BFC84D8D11D872C787AA9A02B1F790>