Ciao Mark,
please, read below...
Regards,
Simone Giannecchini
Ing. Simone Giannecchini
@simogeo
Founder/Director
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 333 8128928
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
On Wed, Jul 24, 2013 at 8:22 PM, Mark Loper <mark_a_loper@anonymised.com> wrote:
All,
I'm trying to write a small white paper covering most everything to do
with a Open Geo installation.
I assume you are talking about GeoServer 
For specific questions about OpenGeo Products you should direct the
questions to them.
The installation will be in an environment
basically focused on WFS rendering. The plan is to use Open Geo to render
As above, I assume you are talking about GeoServer
the features to improve performance in OpenLayers. Currently we're using
KML responses directly from the WFS servers which can take several minutes
to render. We're getting around 100K to 200K features in a response so
asking OpenLayers to render that is slow.
You mean transferring the feature as vectors to OpenLayers and doing
the rendering there? I would not do so even if we
were talking about 1k feature, it would not scale IMHO.
I need to know what the
recommended hardware configuration would be to optimize performance. The
initial install will be a a single node much like MassGIS has set up. If it
does the job functionally we would scale out to several nodes. That said, I
need to be successful up front. All the documentation I can find talks
about the minimum needed. I want to know the best, not the minimum. I'm
looking for Cores, Ram, Disk Space.
Parameters:
Requests are generally around 75K features.
Responses are usually Tiled WMS-C or WMTS.
Features consist of Polygons and points,
How complex are the polygons? How many edges to they have on average.
This can make a huge difference when rendering.
30 concurrent users.
Caching is valid for 30 minutes.
No more than an initial 100 layers of data.
Windows 2008R2 Servers (virtual)
What's the DBMS? SQL Server?
My Thoughts:
4 Cores
16GB Ram
800GB Disk
Thoughts?
Mark
Having GWC in the mix changes things a little bit. Anyay, I believe
this HW setup is unbalanced, too much Memory compared to the #cores
that you have.
Generally speaking knowing the #of concurrent users is not enough you
need to know at least the acceptable average response time.
That said, if you are going to render 75k features in each tile
request you really need to put caching in the mix otherwise if you
multiply this number per the tiles asked by a single users then per
concurrent users you'll get DBMS death as the result
Long storty short, trying to give some indications a viable set up
could be as follows:
- 8 cores
- 2 geoserver instances with integrated geowebcache in active-active
clustering (you can have latest gwc work in active clustering as well)
- give 4 to 6 gb of heap to each instance
With instance I mean different java process, so this means as an
instance two Tomcat installations.
You can find some additional info here:
http://goo.gl/Hd6F5
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users