Hi John,
we are using naviserver on 20-30 installations with quite different
configurations without the symptoms you are describing, so i would
expect a problem in the configuration file.
Is your setup heavy-weight (like OpenACS) or rather light-weight?
If one is running a heavy-weight installation with minthreads 100 (as
you are indicating) with limited resources, the os might kill the
process (or e.g. an oom-killer).
Find a sample configuration files
sample-config.tcl
https://bitbucket.org/naviserver/naviserver/src/ada2e2dd98fde3bd8bfdb4e7ca3531306116705f/sample-config.tcl.in?at=default
openacs-config.tcl
https://bitbucket.org/naviserver/naviserver/src/ada2e2dd98fde3bd8bfdb4e7ca3531306116705f/openacs-config.tcl
Do you experience the "startup problem" with this config files as well?
What is exactly this problem? Is it the case that the server starts and
runs fine, but you do not see multiple connection threads created?
Maybe the server is delivering the files quite fast such it does not need
multiple connection threads?
When you use NaviServer 4.99.5 or newer, the request queue management
is quite different. Under normal operations, incoming requests are not
queued
but directly dispatched to connection threads. Only when all connection
threads are busy, requests are added to the queue. For more details, see:
https://next-scripting.org/xowiki/docs/misc/naviserver-connthreadqueue/
In order to control the eagerness of connection thread creation,
please read the document above or read the comments in the
mentioned config files.
What is the reason for altering minthreads from 1 to 100 and not to a
more sane value
like e.g. 5 or 10?
what version of naviserver + tcl are you using?
Are you experiencing the problem with real web clients
or with a synthetic benchmark?
Is it possible to post the used configuration file here?
best regards
-gustaf neumann
Am 01.01.14 18:57, schrieb John Buckman:
> Hello navifans,
>
> I'm in the process of trying to move to Naviserver from Aolserver.
>
> I'm finding that naviserver is not launching new threads, and is just qeueing
> requests up to be handled by a single thread, despite maxthreads being set
> high.
>
> I can get around that problem if I change
> ns_section "ns/server/${servername}"
> ns_param minthreads 1
> to
> ns_section "ns/server/${servername}"
> ns_param minthreads 100
>
> and then the server *does* use multiple threads. That shouldn't be needed,
> though.
>
> Is there a config parameter I need to twiddle to enable one-demand thread
> creation?
>
> I also have the following two other problems:
> 1) if I try a minthreads of 50 or larger, nsd crashes on startup
> 2) apachebench with a concurrency of 50 causes nsd to crash (at 20 threads)
>
> I'm running debian squeeze, with a number of production aolservers that run
> stably also on the same box.
>
> Any thoughts?
>
> -john
>
>
--
Univ.Prof. Dr. Gustaf Neumann
WU Vienna
Institute of Information Systems and New Media
Welthandelsplatz 1, A-1020 Vienna, Austria
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
