Hi Ravi, On Thu, Jan 6, 2011 at 5:52 PM, Ravi Pavuluri <[email protected]> wrote:
> Hi Justin, > > Thank you for the information. I read the link you sent and it was a very > good one. > > I am looking at both WMS(50%) and WFS(50%) in each application in a tomcat > environment with maximum simultaneous users about 5-10."For smaller > installations that don't typically handle much load we typically use a vm > with 1-2 G of RAM giving about half of it to geoserver." Is this the case > you are referring when you have geoserver as a webapp in Tomcat? Tomcat and > Yes, i am referring to geoserver running in tomcat or some other servlet container. Memory is allocated to the servlet container. > Geoserver both being java based, consume more RAM and you would still > suggest 2GB of RAM with server optimizations? > Yes, but again it depends. The more memory you allocate the more requests you can handle which improves overall availability of your app. So in the end its a trade off and you have to find the balance. > With the above configurations, is 5-6GB RAM with decent processor > considered a safe estimate or an overestimate? > In most production systems I see that do a lot of traffic I usually don't see more than 4G allocated to java/tomcat/geoserver. And even that is a bit excessive. With heap sizes that large you start to pay a big price for garbage collection. I would say with your requirements allocating 2G of ram to java should be more than enough if the server is "properly configured". By properly configured I mean both the services (using control flow, wms limits, etc..) and the data (spatial indexes, attribute indexes based on your SLD styles, etc...) > Thanks, > Ravi, > > > > > ------------------------------ > *From:* Justin Deoliveira <[email protected]> > *To:* Ravi Pavuluri <[email protected]> > *Cc:* [email protected] > *Sent:* Thu, January 6, 2011 11:07:49 AM > *Subject:* Re: [Geoserver-users] Geoserver Production Environment specs > > Hi Ravi, > > It really depends on what you expect the load to be on the server. For > instance if you only expect the server to be accessed by a handful of users > then some pretty modest requirements will probably work. For smaller > installations that don't typically handle much load we typically use a vm > with 1-2 G of RAM giving about half of it to geoserver. For larger setups > obviously the requirement goes up. > > It also matters what type of traffic you will be doing. For instance if you > are strictly doing WMS then the more memory the better since for rendering > the WMS has to continually allocate large chunks of memory for images. > Whereas WFS operates in a strictly streaming fashion. > > There is currently an issue as well in that if you have that many > layers/feature types you will want to change the "feature type cache > settings" (global settings page) to be larger than the number of > layers/feature types. > > Also it is important to properly configure the server in terms of limits. > You should find this article interesting: > > http://opengeo.org/publications/geoserver-production/ > > Hope that helps. > > -Justin > > On Wed, Jan 5, 2011 at 11:02 AM, Ravi Pavuluri <[email protected]>wrote: > >> >> >> Hi, >> >> What would typically be virtual server specs in terms of RAM and processor >> speed you would recommend for production environment to serve several >> applications? >> >> # of Layers served totally from this server ~200 - 250 >> # of Layers simultaneously accessed in an application ~10 >> Data format(vectors only): PostGIS Layers and few shapefiles(max size of >> each 60MB). >> # of simultaneous users : Max 5-10. >> >> Also, does one typically serve all the layers from the a BIG server >> instance or multiple small server instances with small configuration? >> >> I know that this is a very open ended question. Any rough estimate is >> appreciated. >> >> Thanks, >> Ravi. >> >> >> >> >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> Learn how Oracle Real Application Clusters (RAC) One Node allows customers >> to consolidate database storage, standardize their database environment, >> and, >> should the need arise, upgrade to a full multi-node Oracle RAC database >> without downtime or disruption >> http://p.sf.net/sfu/oracle-sfdevnl >> _______________________________________________ >> Geoserver-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/geoserver-users >> >> > > > -- > Justin Deoliveira > OpenGeo - http://opengeo.org > Enterprise support for open source geospatial. > > > -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial.
------------------------------------------------------------------------------ Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
