
Basically, there are some differences that are small, and ignorable, and there are some differences that are really anomalous. And the end of the day, both systems are doing the same thing, so order-of-magnitude performance differences are cries for help.
I've been focussing on the Mapserver side. Last year, the study by Brock and Justin found an odd quirk where Mapserver got progressively worse at shape file rendering as the shape files got bigger. I found the issue and fixed it this spring, and (w00t!) Mapserver won the shape file race this year.
But... this year found that the PostGIS performance in Mapserver was (while fast) about half as fast as Geoserver. Hmmmm. So I know what I'll be working on this month. I have some guesses, but they will need to be tested.
Andrea added some aesthetic tests this year, and brought them to the attention of the Mapserver team, and as a result the next release of Mapserver will include more attractive labeling results and line width control.
Any development team that's willing to swallow their pride (because for every test you win, there's one you'll lose) can get a lot of benefit in joining in this benchmarking exercise.

3 comments:
I find your graphic insightful... as you detailed the progress toward improvements in the servers I noted your runners positioned to race in the wrong direction around the track....
Clearly they are in training to get faster :)
Paul,
Interesting post. It motivated me to convert the mapfiles over to Mapnik xml styles to allow the same benchmarks to be run for Mapnik.
In doing so I've run into a problem with the 'states.shp' shapefile that the geoserver project provides in the benchmarking tests.
Here's the thread that uncovers that fact the dbf is a bit dodgy: http://www.nabble.com/Mapnik-Filter-Expression-Failure-tt20141006.html#a20141526
This shapefile in question is the one used in the #2 Thematic map test and noted in the benchmark readme as 'the states.shp file is a GeoServer demo, whose origin is lost in time.'
It might be useful to use ogr2ogr to fix the shapefile and re-run the tests to confirm that mapserver is not having to take any extra time to handle the dbf.
Post a Comment