1. WMS Performance Shootout Andrea Aime (GeoServer) Jeff McKenna (MapServer)

5. Raster: ECW and GeoTiff mosaics

9. raster read optimization (single pass for multiple bands)

10. enhancing polygon labelling placement

11. EPSG codes caching

12. PostGIS improvements

13. Oracle improvements

15. GML writing speed-ups

16. Raster data access improvements

17. PostGIS data store optimizations

20. Same data backends

22. Data used cannot be modified for display, other than indexing

23. All testing to be done on the same benchmarking machines

24. Hardware Configuration Bench WMS Database JMeter GeoServer MapServer Shapefiles ECW GeoTIFF Oracle PostGIS SDE

26. Apache 2.2

29. SDE 9.3.1

30. PostGIS 1.4.0

33. 4 Xeon Nocona 3.4Ghz, 8 GB RAM

35. 1 x Intel Core2 Duo CPU E6750 @ 2.66GHz / Dual Core, 4Gb RAM

36. 100Gb SATA 3.0Gb/s 7200 rpm HD, OS: RedHat Enterprise 5.3

40. Hot benchmarks are more practical to run

42. Each test uses a random set of requests stored in a CSV file: no two requests in the same run are equal, but all servers perform the same workload

45. The other GIS server is shut down while the tests are run

47. Point layer: gnis_names09 : all location and points of interest names for the state of Texas in the GNIS database. 103000 points, 2.8 MB shapefile, EPSG:4269

48. Line layer, edges_merge : all line elements (rivers and roads) from the TIGER 2008 dataset for the state of Texas. over 5M lines, 1.2GB shapefile, 1.4GB dbf, EPSG:4269

49. Raster layer : Bluemarble TNG, 86400 x 43200 pixels, 7 overview layers (TIF, ECW, tiled 512&8, GeoRaster)

51. This table translates hits per second at sustained peak load in terms of requests per hour and per day

53. Simply fill the polygon in blue, no outline

54. Image scales roughly between 1:10.000 and 1:100.000

55. T1: Shapefiles

56. T1: PostGIS

57. T1: Oracle

58. T1: SDE

60. PostGIS performs roughly 5% better than Oracle on higher loads

61. SDE seems to introduce no overhead compared to direct Oracle access for GeoServer, and a slight overhead for MapServer

62. GeoServer and MapServer have exactly the same performance when the backend is PostGIS and Oracle

64. Each point is rendered using a little GIF/PNG graphics

65. T2: shapefiles

66. T2: PostGIS

67. T2: Oracle

68. T2: SDE

70. T3: shapefiles

71. T3: PostGIS

72. T3: Oracle

73. T3: SDE

75. T4: shapefiles

76. T4: PostGIS

77. T4: Oracle

78. T4: SDE

80. ECW file is 260MB

81. TIFFs are uncompressed, tiled, with overviews. Around 16GB for each mosaic

82. T5: ECW

83. T5: 512 tiles mosaic

84. T5: BigTiff vs 8 tiles tiff GeoServer cannot do BigTiff, so a 8 tiles mosaic was used (almost 2G B per tile)

86. Fixed problem with 5.6.0-beta for SDE layers

88. Fixed problem with ECW crashes under high load

90. Put the servers under a faster internet connection for quicker data transfers and tests setups

91. Modify the number of parallel client requests performed so that the 2-4-8 parallel clients case gets exposed

92. Phases/cycles for benchmarking – to allow for teams to interpret results and make software enhancements

93. Reprojection in both vector and raster data

94. Audience suggestions?

96. Wiki home: http://wiki.osgeo.org/wiki/Benchmarking_2009

97. Mailing list: http://lists.osgeo.org/mailman/listinfo/benchmarking

98. Additional MapServer Results (not presented)

99. MapServer Roads/Lines Test Results

100. MapServer Labelled Roads/Lines Test Results

101. MapServer Polygon Test Results

102. MapServer Point Test Results

103. MapServer Raster Test Results