Re: [Exist-open] Standalone server threads

[Gene S. <ge...@tr...>]

Hi Wolfgang,

(sorry I forgot to copy the list)

Thanks very much; this helped.  I was able to climb from about 32 updates
per second to about 43/s against different docs in the same collection on a
single processor, 512MB Xen-based VM, though my app has known inefficiencies
still.  I have access to better hardware than this, but still I think that's
pretty decent for this little hub. ...having spent a couple years working
with Berkeley DB XML wrapped in a custom server, this definitely feels like
an improvement.

The documentation at http://www.exist-db.org/deployment.html#N1026B states
that "-t" is used for changing the number of threads assigned to client
requests, which I read as referring to jetty.  That said, your suggestion
was easy to implement.

The work on this project is admired and appreciated.  Thanks a bunch

- Gene Stevens


On Wed, Mar 18, 2009 at 2:52 AM, Wolfgang <wol...@ex...> wrote:

> Hi,
>
>  The only problem I seem to have is that I apparently cannot successfully
>> alter the number of threads the standalone server is using (5 by
>> default). The documentation at http://www.exist-db.org/deployment.html
>> indicates that you can send "-t XX" to the "server.bat" script
>> ("server.sh" in my case). However, no matter what value I send, it
>> always seems to be exactly "5".
>>
>>
> The -t parameter specifies the number objects eXist uses to handle
> low-level database requests internally. It has nothing to do with the number
> of threads provided by the web server.
>
> The standalone server uses a fixed jetty configuration, created by class
> org.exist.StandaloneServer. If you look into that file, you'll find two
> lines:
>
> ((ThreadedServer)listener).setMinThreads(5);
> ((ThreadedServer)listener).setMaxThreads(50);
>
> You could try to change those and recompile with build.sh to see if you get
> more threads.
>
> Wolfgang
>



-- 
Gene Stevens
http://gene.triplenexus.org