Wms Performance Tests Map Server Vs Geo Server

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

more share options
Embed For WordPress.com

Without related presentations

Notes on slide 1

Introduction to uDig 2/13/05 Brock:

Introduction to uDig 2/13/05 Brock: WMS Performance

Introduction to uDig 2/13/05 Justin: -explain the two out of the box behave quite differently - fast cgi vs database connection pooling - tried to make as equal possible ==> GeoSever doing < 1 bit png output (ask andrea about appropriate terminology)

Introduction to uDig 2/13/05 Justin: - Breif overview of WMS for the layman WMS Performance

Introduction to uDig 2/13/05 Brock: WMS Performance

Introduction to uDig 2/13/05 Brock: - random bounding box generation - exact same requests for each server - 10,000 subset of 3 million WMS Performance

Introduction to uDig 2/13/05 Brock: Response time in milliseconds on the Y-axis. Three interesting ways to look at the graph - PostGIS vs. Shapefile - Indexing (large data set vs. small data set) - Mapserver vs. Geoserver - Geoserver had many code changes to improve performance. WMS Performance

Introduction to uDig 2/13/05 Justin: - explain how the concurrency, we chose a “worst case” concurrency model, there are many others WMS Performance

Introduction to uDig 2/13/05 Justin: - suprising results - expected postgis to perform much better under a load - however, read-only access means no locking for shapefiles - Mapserver with fast cgi with 20 processes - GeoServer with connectino pooling at 20 connections WMS Performance

Introduction to uDig 2/13/05 Justin: - same data, different metric, througput - mapserver remains consistent for longer, geoserver starts to degrade around 15 concurrent requests (garbage collector?) Wms Performance

Introduction to uDig 2/13/05 Brock: This test only scratches the surface. At least it gives a sense of how much on-the-fly reprojection affects response time. WMS Performance

Introduction to uDig 2/13/05 Brock: What is FastCGI? Conclusion: use FastCGI unless you have compelling reasons no to. WMS Performance

Introduction to uDig 2/13/05 Brock WMS Performance

Introduction to uDig 2/13/05 WMS Performance

Introduction to uDig 2/13/05 Justin WMS Performance

Introduction to uDig 2/13/05 WMS Performance

Introduction to uDig 2/13/05 Brock does mapserver Justin does GeoServer - out of the box geoserver much slower ==> defautl 24 bit rendering, logging on, default styling has transparency , anti-aliasing on by default

Introduction to uDig 2/13/05 Brock WMS Performance

Introduction to uDig 2/13/05 WMS Performance

Introduction to uDig 2/13/05 Introduction to uDig

Introduction to uDig 2/13/05 WMS Performance