[Geoserver-users] Hardware recommendations for GeoServer?

Hi
I am in the process of ordering a virtual server for GeoServer from our IT
department. GeoServer will be used for cascading WMS, as well as services
using PostGIS data. I expect a handful of users (mostly QGIS) in the
beginning, but I imagine demand will increase quickly with more users and
web maps consuming the services from GeoServer. Any thoughts on hardware
recommendations for this case, for example RAM?

Regards,

Magnus

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Hardware-recommendations-for-GeoServer-tp5270831.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

For us, the biggest improvement came by putting our database on SSDs. We have ample memory and processing power though. So the system is always IO bound. Also, this would be specific to vector data in PostGIS, for example OSM. If you’re doing a lot of imagery or other raster data, then the gain may not be as pronounced. Just a guess, haven’t tried that yet.

···

On Thu, Jun 9, 2016 at 6:38 AM, johnrobot <johnrobot@anonymised.com> wrote:

Hi
I am in the process of ordering a virtual server for GeoServer from our IT
department. GeoServer will be used for cascading WMS, as well as services
using PostGIS data. I expect a handful of users (mostly QGIS) in the
beginning, but I imagine demand will increase quickly with more users and
web maps consuming the services from GeoServer. Any thoughts on hardware
recommendations for this case, for example RAM?

Regards,

Magnus


View this message in context: http://osgeo-org.1560.x6.nabble.com/Hardware-recommendations-for-GeoServer-tp5270831.html
Sent from the GeoServer - User mailing list archive at Nabble.com.


What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e


Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Jason Newmoyer
Newmoyer Geospatial Solutions
843.606.0424
jason@anonymised.com

GeoServer is usually hamstrung based due to disk or cpu for vector data, when working with raster data (or complicated styling) the system can respond well to more memory. You will not get any specific advice hardware requirements will be based on your data and expected load.

···

On 9 June 2016 at 03:38, johnrobot <johnrobot@anonymised.com> wrote:

Hi
I am in the process of ordering a virtual server for GeoServer from our IT
department. GeoServer will be used for cascading WMS, as well as services
using PostGIS data. I expect a handful of users (mostly QGIS) in the
beginning, but I imagine demand will increase quickly with more users and
web maps consuming the services from GeoServer. Any thoughts on hardware
recommendations for this case, for example RAM?

Regards,

Magnus


View this message in context: http://osgeo-org.1560.x6.nabble.com/Hardware-recommendations-for-GeoServer-tp5270831.html
Sent from the GeoServer - User mailing list archive at Nabble.com.


What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e


Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users


Jody Garnett

Thank you for your thoughts, this will help when setting up the server.

Magnus

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Hardware-recommendations-for-GeoServer-tp5270831p5271325.html
Sent from the GeoServer - User mailing list archive at Nabble.com.