Closed Bug 266940 Opened 20 years ago Closed 20 years ago

MAX_THREADS in selfserv should be higher

Categories

(NSS :: Tools, defect, P2)

3.9.3
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: julien.pierre, Assigned: julien.pierre)

Details

It should be possible to test selfserv with much higher threadcounts, at least
1024, perhaps 4096. 

This is especially treacherous because the code prints out that it's using the
number of threads passed on the command-line, even if it's actually been limited.
Priority: -- → P2
Target Milestone: --- → 3.10
Actually, selfserv displays the actual number of threads, so only MAX_THREADS
needed to be changed. I have bumped it to 4096 . It's possible to start a
process with that many threads fairly quickly.

I tried with 64K threads earlier but it was just taking too long to even start
the selfserv process on Solaris, even with 2GB of RAM and dual Ultrasparc III
CPUs, so I didn't think it should be that high.

Checking in selfserv.c;
/cvsroot/mozilla/security/nss/cmd/selfserv/selfserv.c,v  <--  selfserv.c
new revision: 1.59; previous revision: 1.58
done
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Maybe max_threads should be overridable from the command line.
I'm not sure 4K is a good choice for the default.
You need to log in before you can comment on or make changes to this bug.