Re: [Geoserver-users] Geoserver and number of threads

[Andrea A. <and...@ge...>]

On Tue, Mar 15, 2011 at 7:49 PM, Boubakar <bou...@gm...> wrote:
> Hello,
>
> We're using a Geoserver, and we've a performance problems in production with
> a large number of users.
>
> We've made some load test with : 250, 150, and 20 threads. We've noticed
> that Geoserver works better with 20 threads than with 150 threads, and when
> thread number increase (150 or 250), performance decrease.
>
> Is it normal ? How Geoserver manage the users request ? Does Geoserver use
> asynchronous strategy to manage users request ?

It is normal. Anedoctal evidence shows you get to use 100% of your cores
when you have 2 to 4 GetMaps per core, past that it can only get worse.

That's one of the reason why I've made the control-flow module time ago,
if you want to run at peak performance you should stop at the point
where you already use 100% of your resources and start queuing requests
instead of executing them in parallel.
The docs page lists other reasons why using control flow is useful:

http://docs.geoserver.org/2.1.x/en/user/community/controlflow/index.html

Btw, that module works only in recent builds, don't try to use it against
2.0.2 or it will lock up your server

Cheers
Andrea

-- 
-------------------------------------------------------
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead

Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy

phone: +39 0584 962313
fax:      +39 0584 962313
mob:    +39 333 8128928

http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf

-------------------------------------------------------