Difference between revisions of "Toronto Code Sprint 2009 Agenda"

From OSGeo
Jump to navigation Jump to search
(New page: == Theme == '''The Need for Speed...''' Performance is the universal feature, and the latest [Geoserver vs Mapserver http://blog.geoserver.org/2008/10/22/geoserver-benchmarks-at-foss4g-2...)
 
Line 3: Line 3:
 
'''The Need for Speed...'''
 
'''The Need for Speed...'''
  
Performance is the universal feature, and the latest [Geoserver vs Mapserver http://blog.geoserver.org/2008/10/22/geoserver-benchmarks-at-foss4g-2008] results indicate that there are places throughout the C stack that can use improvement.
+
Performance is the universal feature, and the latest [http://blog.geoserver.org/2008/10/22/geoserver-benchmarks-at-foss4g-2008 Geoserver vs Mapserver] results indicate that there are places throughout the C stack that can use improvement.
  
 
== Proj4 ==
 
== Proj4 ==

Revision as of 16:05, 19 January 2009

Theme

The Need for Speed...

Performance is the universal feature, and the latest Geoserver vs Mapserver results indicate that there are places throughout the C stack that can use improvement.

Proj4

  • Run Mapserver under load and review where Proj4 takes a hit (everywhere)
  • Caching of PJ structs, Should make QGIS and Mapserver faster.
  • Parsing of proj strings. Switching from the hand-coded parser to flex-generated parser might yield some improvement.

Mapserver

  • Run the Geoserver benchmark tests under profiler and review results
  • Single-pass querying, will bring WFS speed up to par
  • Mapserver as Apache module, removes FastCGI instability and is potentially even faster, see [#2565 http://trac.osgeo.org/mapserver/ticket/2565]

GDAL

  •  ?

PostGIS

  • Roadmap for 1.5+
  • New on-disk format? Aligned double?
  • New GEOS coordinate sequence to bind on top of aligned PostGIS structures?
  • Profiling and review profile results

GEOS

  • Administrivia, what to do without a full-time maintainer?
  • Roadmap for 3.2?