Hello Joel!

Thursday February 15 1996 14:49, Joel Downer wrote to Doug Nazar:

JD> Doesn't OS/2 place a limit on the number of active threads?  If so, and
JD> given that some people might want to run very large BBS'es on an OS/2
JD> LAN (100+ nodes), couldn't there be some problems with this approach?
JD> I'm not aware that there's any reason that a 100-thread server process
JD> is *impossible*, but isn't that a log of resources to hog for one door?

The THREADS= config.sys parameter sets the maximum thread count (upto
4096). Each thread does comsume some resourses but anyone who can afford a
hundred-line bbs should be able to afford the memory .

JD> Forgive me if this is another dumb question... I make no claims to
JD> expertise here.   It sounds as if what I'd need to do to avoid
JD> piggishness (at very least) is have one "listener" thread
and then spawn
JD> a new thread for each actual "hit" (rather than spawning MaxNodes
JD> threads at startup).

This is another aproach. However, I should point out that a blocked thread
(in this case, blocked on DosConnectNPipe) uses no CPU time. The only
sluggishness would be do to swapping if they didn't have enough memory.

Doug

--- GoldED/2 2.50+