Hi Robert,
I think 2GB server side is fine for Development, but to release to the public
as a production is too low.
The minimum I would have is 4GB – and this would probably only give you a
descent amount of capacity for 5 concurrent requests.
You should also think about scale thresholds set in the SLD of your data – it
is not so good to be large scale mapping at small scales – it will kill your
server.
Just some considerations.
Cheers,
Steve
From: Robert Buckley [mailto:robertdbuck...@yahoo.com]
Sent: 28 June 2011 10:06
To: geoserver-users@lists.sourceforge.net
Subject: [Geoserver-users] Geoserver Architecture: How to assess effectiveness
Hi,
after a long summer break of 8 weeks I am now back into things. At the top of
my list is the further development of a wms/wfs service for my local authority.
I have been "practising" with a Linux
Ubuntu/Tomcat6/Geoserver/PostgresSQL/Postgis/geoExt setup for a while now (1
year) and have a few app up and running. I am now in a position to start
thinking about releasing the application in the public, but am unsure about the
performance of my setup.
My hosted 32bit server has 2gb Ram and 25gb storage space. The application
which I have developed do not serve data very fast. What I am trying to find
out is whether this is due to my javascript coding methods, the Geoserver
setup, Tomcat6 configuration, Postgis responsiveness or server performace
limitations.
One app can be tested here.
http://maps.zgb.de:8080/geoserver/www/testing/wea.html
I find that the loading time varies considerably on different PCs. I have a
WinXP Desktop with 3gb ram, and the loading time is acceptable. My my colleague
who is also using XP but with only 1gb the loading time can be up to 30sec-
min. Firebug shows that the ows/geoserver takes the longest time to serve.
I thought the local pc performance should have little affect upon server based
apps, but obviously this is not the case. Even the browsers can make a huge
difference as far as I can tell or even browser add-ons which have been
installed.
Can anyone give me any tips on how to weed out the typical problems when
building a geoserver based app?
Thanks for any tips,
Robert Buckley
________________________________
DISCLAIMER:
This email may contain confidential information and is intended only for the
use of the specific individual(s) to which it is addressed. If you are not the
intended recipient of this email, you are hereby notified that any unauthorized
use, dissemination or copying of this email or the information contained in it
or attached to it is strictly prohibited. If you received this message in
error, please immediately notify the sender at Infotech or
mail.ad...@infotech-enterprises.com and delete the original message.
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
