[Opensim-dev] Threading strategy

[Dalien Talbot]

How would the thread pool help ? IMHO the threads should be per-region, not
per-client - then the number of threads would be quite limited.

I would think in the http server the thread pool is used because HTTP is
inherently a request-response-forget protocol. Whereas the client
connections are long-lived, so if we have now one thread per client
connection, I do not see how the thread pool would be useful...

(indeed these are speculations without much looking at the code, the tide of
the last week's burst of RL still there)

/d

On 9/23/07, Tleiades <tleiades at hotmail.com> wrote:
>
>  Hi
>
> I have created a new page on the wiki, outlining the threading strategy,
> or lack thereof.
>
> http://opensimulator.org/wiki/OpenSim:Threading_strategy
>
> I think we should streamline our use of threads. I am especially concerned
> about the way threads are used in the ClienView, where a thread is used per
> client. One thread per connection is *the* classical way of handling
> several clients connecting to a single server, unfortuantely this frequently
> leads to a scenario where hundreds, if not thousands of threads execute in
> one process. I would suspect that the user, asset and grid servers will have
> a large number of connections, consequently we need to think ahead, and plan
> for good scalability in those server modules.
>
> I would propose that we generally switch to a strategy similar to the one
> used in BaseHttpServer, relying on the thread pool.
>
> /tleiades
>
>
>
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://opensimulator.org/pipermail/opensim-dev/attachments/20070924/21c6719e/attachment-0001.html>