[GIS] Performing GIS benchmarks

benchmarkperformance

I was searching the web for benchmarks (but couldn't find any) that would indicate hardware performance (probably cpu in particular) in different GIS software in time consuming tasks (like hillshade generation, raster reproject, topology buildup), not for the purpose of comparing different GIS software but to compare performance for different cpus, multithreading impact, ssd, etc. If i started with that, I suppose i'd need a standarized set of data, publicly available so anyone could try and post results. But does anyone know if such comparisons already exist anywhere?

Best Answer

At FOSS4G they perform a Benchmark test every year against various WMS Servers. Being in the Open Source spirit, they use free datasets, document everything, and release the source code so you can probably pick what you want from it.

You can find out a little more from the wiki page: http://wiki.osgeo.org/wiki/FOSS4G_Benchmark

Unfortunately it looks to be a poorly maintained wiki and many pages don't like to other relevant pages so you'll have to search a bit to find everything (its scattered around). http://wiki.osgeo.org/wiki/Category:Benchmarking might be a good place to start.

They also have results where they discuss things like what was limiting stuff, including hardware, i.e. from slashgeo

This year, benchmark includes bottlenecks from CPU, disk access, network access and remote database access.

Related Solutions

PostGIS Bounding Box – How to Perform Bounding Box Query in PostGIS

Assuming the given bounding box limits are in the same spatial reference system as the stored coordinates, and you know which spatial operator (intersects or contained by) you need:

SELECT *
FROM   my_table
WHERE  coordinates 
    && -- intersects,  gets more rows  -- CHOOSE ONLY THE
    @ -- contained by, gets fewer rows -- ONE YOU NEED!
    ST_MakeEnvelope (
        xmin, ymin, -- bounding 
        xmax, ymax, -- box limits
        my_srid)

Alternatively, if you prefer the sound of "contains" (instead of "contained by") the WHERE clause should be flipped:

WHERE  ST_MakeEnvelope (...)
    ~ -- contains, gets same fewer rows 
    coordinates

PS: Given (by OP after the above was posted) that the records are simple points, I think that the difference between "intersects" and "containment" becomes very subtle, affecting only the points on the edges of the bounding box.

Best Answer

Related Solutions

PostGIS Bounding Box – How to Perform Bounding Box Query in PostGIS

Related Question