1

This question is an exact duplicate of:

I have an application which access same map from two geoserver using loadbalancing concept the map is accessed using WMS service. where the two geoserver connected to a single same POSTGIS database. even the both tomcat is alloted with 3GB of RAM but the map rendering is still too slow

Is this have anything to do with the performance of POSTGreSQL??

is there any way to increase map availability ?

Please help me

marked as duplicate by PolyGeo, blah238, radouxju, Ian Turton Apr 3 '14 at 16:11

This question was marked as an exact duplicate of an existing question.

  • 1
    What efforts have you made to measure it and see? Do you log query durations on your PostgreSQL server? Check out PgBadger, pg_stat_statements, log_query_min_duration, etc. There are also request performance tools for appservers like Tomcat that can tell you what parts of your code spent the longest time waiting. You can also use system level metrics (load, cpu, memory utilization, I/O load, etc) to reason about bottlenecks in performance. Don't guess, measure! – Craig Ringer Mar 31 '14 at 5:19
  • thanku Craig for your response will u please give me some tutorial to measure the performance really am new to all these – Anas A Mar 31 '14 at 5:29
  • 1
    wiki.postgresql.org/wiki/Performance_Optimization and the numerous links from there. Time to start studying, there's lots to learn. Or, if you don't have the time to study, postgresql.org/support/professional_support – Craig Ringer Mar 31 '14 at 5:34
  • 1
    Is GeoWebCache enabled for your GeoServers? Have you installed the native JAI and JAI Image I/O extensions? A lot of factors can affect the GeoServer rendering performance, as stated here: docs.geoserver.org/stable/en/user/production/index.html – Sorin Călinică Mar 31 '14 at 7:17
  • did you follow the suggestions here docs.geoserver.org/stable/en/user/production/index.html – Ian Turton Mar 31 '14 at 10:06
1

You must understand that load balancing works for high-traffic sites. Your problem seems to be related with the fact that tiles are created on the fly from the DB, instead of created on the DB once and then being cached in your server.

Perhaps adding a caching solution for tiles might help: Check http://giscollective.org/tutorials/web-mapping/wmsseven/ for possible solutions.

Such a solution for GeoServer would probably be GeoWebCache as already others have suggested.

Not the answer you're looking for? Browse other questions tagged or ask your own question.