Benchmarking 2011

Basic Premise
Following up on last year's exercise, the performance shoot-out presentation at FOSS4G2011 will test how long each Web mapping server takes to generate a map image, from a common set of spatial data, on a common platform. The data will be served by each Web mapping server through the WMS standard, which will serve exactly the same set of LAYERS. A JMeter load will be run on the testing box to measure various aspects of those layers.

Communication
Coordination/communication is primarily via the Benchmarking mailing list: http://lists.osgeo.org/mailman/listinfo/benchmarking

Weekly meetings will occur through IRC chat in the #foss4g channel on irc.freenode.net (you can use webchat to connect in browser)

Next IRC Meeting

 * Wed August 3rd, 2011 @ 14:00:00 UTC
 * Provisional Agenda:
 * Status of OSM vector styling from all teams
 * Discuss rasters to be used
 * Discuss testing methodology

Previous IRC Meetings

 * Meeting Log

Participants
Server Teams:

Data Teams:

Not Participating:

Rules of Engagement (DRAFT)

 * 1) All parties must contribute any changes that they make to their software for this exercise, back to their community. Note that the changes don't have to be contributed before the conference, just in a reasonable period of time.
 * 2) Comparisons will be made of the best available version of the software, be it a formal release or a development version.
 * 3) One test will be run: a 'baseline' test with the data in any format desired, but teams cannot generalize or change the data's resolution from its raw values.
 * 4) Teams must document all steps they did to manipulate the data/server (such as spatial indexes created etc.).  If a team does not document the steps on this wiki then that team's test results will not be used.
 * 5) WMS output formats to be used will be png8 and png24 where possible

Documenting Server Setup
It is the responsibility of each team to document their setup with regard to configuration details, setup notes, and differences between other servers in how data might be accessed/indexed.

Notes for each server:


 * Mapnik
 * Cadcorp
 * MapServer
 * QGIS Server

Stylesheets and scripts in svn using a directory named wms/{year}/{servername}:


 * Mapnik
 * Cadcorp
 * MapServer
 * QGIS Server

Testing Tool
JMeter is used since it can read a list of bbox's via CSV, and the machine that applies load has been updated with Jmeter 2.5 (the latest stable release at the time of the benchmark): http://www.reverse.net/pub/apache//jakarta/jmeter/binaries/jakarta-jmeter-2.5.zip

Jmeter can be run from the command line like:

/home/jmeterusr/jakarta-jmeter-2.5/bin/jmeter

Server Ports
Each server has access to a range of ports for testing:

Mapserver - 8080 - 8089

Mapnik - 8090 - 8099

Cadcorp - 4326 - 4335

Constellation - 8100 - 8109

GeoServer - 8110 - 8119

OSM Vectors

 * Benchmarking_2011/DB_Schema
 * Benchmarking_2011/Imposm

CSV Files created with

Sample styling:


 * mapserv6
 * MapServer Linux (with OpenLayers)
 * MapServer Win64 (with OpenLayers)


 * mapnik

DEM Hillshading
Sample styling:


 * MapServer 6 Hillshade

DEM Hillshading + OSM Vectors

 * MapServer 6 Hillshade + OSM Vectors - Linux Win64

OSM Vector Style changes: LandN layers turned off (they provide background color) LanduseN layers set to 70% opacity

Running JMeter
JMeter is run using VNC (port 5901) on the Jmeter server.

JMeter Results
There are 2 scripts for summarizing and ploting the JMeter results from benchmarking

1). opt/scripts/2011/jmeter/charts/plotter.py Takes 3 arguments 1). The jmeter output 2). A String to put on the title of the chart 3). Normal or seed to determine how many thread loops

Example usage:

2). /opt/scripts/2011/jmeter/charts/summarizer.py

This will produced the summary tables from the Jmeter results

Example usage:

SVN

 * The project files (minus data) are stored in Subversion (http://svn.osgeo.org/osgeo/foss4g/benchmarking/wms/2011/). If you need commit access contact jmckenna on IRC.


 * Data are only stored on the server at '/benchmarking/wms/2011/data/'


 * existing committers can add new OSGeoID users through this page: https://www.osgeo.org/cgi-bin/auth/ldap_group.py?group=osgeo

Hardware
Contact [User:msmitherdc|Michael Smith] with any questions about this hardware or for login credentials.

windows_wms_bm (windows server)
 * System Type:  Dell PowerEdge R410
 * Ship Date:   7/7/2010
 * Processor: Intel® Xeon® E5630 2.53Ghz, 12M Cache,Turbo, HT, 1066MHz Max Mem
 * 8GB Memory (4x2GB), 1333MHz Dual Ranked RDIMMs for 1Processor, Optimized
 * 2TB 7.2K RPM SATA
 * OS: Windows Server 64bit

linux_wms_bm (linux server)
 * System Type: Dell PowerEdge R410
 * Ship Date:   7/7/2010
 * Processor: Intel® Xeon® E5630 2.53Ghz, 12M Cache,Turbo, HT, 1066MHz Max Mem
 * 8GB Memory (4x2GB), 1333MHz Dual Ranked RDIMMs for 1Processor, Optimized
 * 2TB 7.2K RPM SATA
 * OS: Centos 5.5 x86-64

External Related Links

 * FOSS4G2010 Benchmarking Presentation
 * FOSS4G2009 Benchmarking Presentation
 * FOSS4G WMS Benchmark
 * WMSTester - tool for testing not from OSGeo