Hi,
We are using GeoServer for a small Webmapping application and it works fine.
Now we are asked to be able to add lots (hundreds) of users. Which means heavy
load and scalability. And probably roughly 10 getmap / sec.
But we're having a hard time to figure out if geoserver is the right tool and
if yes, how many servers/CPUs should be added and how to calculate the right
number of tomcat per server, thread per tomcat, etc.
Of course we plan to do benchmarks but a rough idea would be welcome...
I have read all I could find regarding geoserver in production, on steroids,
etc. but I still have questions & concerns :
Knowing that we just want geoserver (inside of Tomcat on Linux) to publish WMS
and WFS services based on geospatial data stored in an Oracle database :
1. Our database is SDE but with Oracle SDO storage : for the best
performances, should we use the SDE or the Oracle Spatial connector ?
2. I am really concerned by all I could read about Java2D not scaling
well. Is it still the case ? It looks like switching off antialiasing cures the
problem. Is that right ?
3. Is there a rule of thumb for correctly spanning tomcats across
CPUs/Cores/Threads and servers
4. What's the best JDK flavor and version ?
5. Anything else I may be missing...
If anybody has leads or good ideas it would be welcome.
Regards,
Laurent
PS : my boss would not mind sticking with ArcGIS Server (which we know pretty
well) but I would like to be able to show that GeoServer is a real alternative.
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
