I would like to know if there is anyway to speed up geoserver as I seem to be
running out of options.
I have a base layer map that has 15 items on it that is need to make the map
look decent.
I have also added the native JAI and the Native JAI ImageIO installed and
its reading it although I had
Ravyn,
what is the source of the data? A database or shapefile? By 15 items do
you mean 15 layers?
GeoWebCache caching allows GeoServer to store WMS images for reuse by
subsequent requests, making it much, much faster:
http://docs.geoserver.org/stable/en/user/geowebcache/
Google Maps uses a
Hi Ravyn,
could you please provide some more details about the data you are rendering?
Which type of data are you serving? Is it raster data? In that case, which
format is?
Please, let us know so we can provide you more suggestions.
Best Regards,
Daniele
==
Our support, Your Success! Visit
And you might also consider production-grade changes such as increasing
the Java heap size:
http://docs.geoserver.org/latest/en/user/production/
http://docs.geoserver.org/latest/en/user/production/container.html#optimize-your-jvm
--
Ben Caradoc-Davies ben.caradoc-dav...@csiro.au
Software
The source data is a database. Yes I mean 15 layers in the base map.
I have had a look at the geowebcache and copied the war file in the apache
tomcat webaps folder but for some reason when I click on it , it gives me a
whole error file list so I am not to sure what exactly I'm doing wrong with
Rayvn,
please do not copy GeoWebCache into GeoServer as there is already a
GeoWebCache version bundled in the GeoServer WAR. Instead, configure
GeoWebCache using the GeoServer web administration interface GeoWebCache
page.
Please also consider database optimisations such as indices, both
Hi Ravyn
(Sorry for the direct reply, this one goes to the list instead)
The source data is a database. Yes I mean 15 layers in the base map.
In our experience, and I am sure that many here will agree, there are
then several things you could look at DBS, Geoserver, caching, and
clustering - the
I must concur with Greg; we have a layergroup that has layers from about 60
different database tables, though only up to 15 are visible at any one
time. This takes along time to render (up to a full minute) - and after
investigation it appears this is because of the database/GeoServer
I am using postgreSql with geoserver.
Ok will try to get that sorted out then with the geowebcache.
I do have indexes with all my tables I know I have I think just the normal
indexes so maybe need to look at the other type too.
thanks
--
View this message in context:
I have tried to add these
http://docs.geoserver.org/latest/en/user/production/container.html#optimize-your-jvm
http://docs.geoserver.org/latest/en/user/production/container.html#optimize-your-jvm
but for some reason that seems to keep breaking the geoserver bit it does
not seem to allow me to
I keep getting a HTTP Status 500 - Servlet.init() for servlet geowebcache
threw exception error when I try and access the geowebcache.
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Geoserver-to-run-faster-tp5086061p5086343.html
Sent from the GeoServer - User mailing
On Tue, Oct 29, 2013 at 12:30 PM, Ravyn smrcoutt...@gmail.com wrote:
I am using postgreSql with geoserver.
Ok will try to get that sorted out then with the geowebcache.
I do have indexes with all my tables I know I have I think just the normal
indexes so maybe need to look at the other type
Hi all
My database has about 115,000 tables in GEOSERVER they are represented as
127,000 layers and layers of group 18000
The first building WMS composes about 5 minutes after it's generated tiles goes
very quickly.
But all the same the first request, are very slow
Sorry for my bad English
Hi Ravyn,
I am using postgreSql with geoserver.
I do have indexes with all my tables I know I have I think just the normal
indexes so maybe need to look at the other type too.
Ok, so - as Andrea also states - you will definitely need some spatial indexes.
Look into that further - for
14 matches
Mail list logo
