Re: maxproc limits
On Fri, Oct 06, 2017 at 04:06:15PM +0100, Stuart Henderson wrote: > I have been bumping into maxproc limits a lot recently on my > workstation. While I do have quite a lot of processes at times, I don't > think I have quite been tripping into the limits of number of actual > processes. > > It seems that perhaps threads are counted towards these. Is that > expected/desirable? If so, would it be sane to raise the defaults > in login.conf and NPROCESS? 1310 isn't a lot when chromium is > using 500+. Somewhat related, I think that pbuild defaults on amd64 should be bumped. (lots of cpus, and enough address space to take advantage of it) I regularly run into a few ports I have to restart because I ran into the maxproc limits. But then, 32 CPUs...
Re: maxproc limits
On 2017/10/06 13:51, Ted Unangst wrote: > Stuart Henderson wrote: > > I have been bumping into maxproc limits a lot recently on my > > workstation. While I do have quite a lot of processes at times, I don't > > think I have quite been tripping into the limits of number of actual > > processes. > > > > It seems that perhaps threads are counted towards these. Is that > > expected/desirable? If so, would it be sane to raise the defaults > > in login.conf and NPROCESS? 1310 isn't a lot when chromium is > > using 500+. > > kern.maxthread defaults to 1950. i have no idea what logic the formula is > attempting to express. each user will run one multithreaded process of 8 > threads? huh? > > conf/param.c:intmaxthread = NPROCESS + 8 * MAXUSERS; > Ah, I missed the separate kern.maxthread. I'll at least bump that locally then (I had already bumped maxproc). I have some java crap as well, when that's running alongside chromium there aren't many free.
Re: maxproc limits
> Stuart Henderson wrote: > > I have been bumping into maxproc limits a lot recently on my > > workstation. While I do have quite a lot of processes at times, I don't > > think I have quite been tripping into the limits of number of actual > > processes. > > > > It seems that perhaps threads are counted towards these. Is that > > expected/desirable? If so, would it be sane to raise the defaults > > in login.conf and NPROCESS? 1310 isn't a lot when chromium is > > using 500+. > > kern.maxthread defaults to 1950. i have no idea what logic the formula is > attempting to express. each user will run one multithreaded process of 8 > threads? huh? > > conf/param.c:intmaxthread = NPROCESS + 8 * MAXUSERS; Logic? It doesn't need to be logical. It is attempting to invent some sort of limit. If there isn't some sort of limit on resource allocation, all sorts of worse problems can pop up.
Re: maxproc limits
Stuart Henderson wrote: > I have been bumping into maxproc limits a lot recently on my > workstation. While I do have quite a lot of processes at times, I don't > think I have quite been tripping into the limits of number of actual > processes. > > It seems that perhaps threads are counted towards these. Is that > expected/desirable? If so, would it be sane to raise the defaults > in login.conf and NPROCESS? 1310 isn't a lot when chromium is > using 500+. kern.maxthread defaults to 1950. i have no idea what logic the formula is attempting to express. each user will run one multithreaded process of 8 threads? huh? conf/param.c:intmaxthread = NPROCESS + 8 * MAXUSERS;
maxproc limits
I have been bumping into maxproc limits a lot recently on my workstation. While I do have quite a lot of processes at times, I don't think I have quite been tripping into the limits of number of actual processes. It seems that perhaps threads are counted towards these. Is that expected/desirable? If so, would it be sane to raise the defaults in login.conf and NPROCESS? 1310 isn't a lot when chromium is using 500+.
