Yes, your suggested scenario with (1) and (2) is a possible explanation (albeit not the only one)
Each thread has a specific purpose for aolserver, and only a subset of the threads are those that process connection requests. So, even though the server may be very active, it is not unusual to have some portion of threads sitting relatively idle - even as new threads are being spawned. Regarding the activity/purpose of any specific thread, you can use "ns_info threads" to gain some insight on that (although you may or may not be able to easily relate each thread to its respective ps output). -Elizabeth Bernd Eidenschink wrote on 2/19/04, 3:18 AM: > Hi Elizabeth, > > thanks for your reply. What I don't know right now is how to interpret > (1) against (2) (see below). > (1) started Feb05 and the TIME column reports 00:00:00, whereas (2) > started Feb15 and reports 00:38:00. > > Does this mean that (1) is a thread waiting for some ns_schedule_proc > (e.g.) job whereas (2) is a connection thread doing heavy work? > > On a development machine hitting AOLserver with concurrent users (using > http_perf) the server started finally (and temporarily) 20 threads with > about 4-6 doing nothing (0% CPU). > > Regards, > > Bernd. > > ------------------------ > > # ps -afx -o user,pid,ppid,start_time,time,command > > PID PPID START TIME COMMAND > (1) > 22185 22184 Feb05 00:00:00 \_ [...]/nsd -izt [...]/c.cfg [-u / -g] > > (2) > 32514 22184 Feb15 00:38:00 \_ [...]/nsd -izt [...]/c.cfg [-u / -g] > > > -- > AOLserver - http://www.aolserver.com/ > > To Remove yourself from this list, simply send an email to > <[EMAIL PROTECTED]> with the > body of "SIGNOFF AOLSERVER" in the email message. You can leave the > Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
