Performance tuning

There are several measures you can take to improve the performance of applications that use spatial data.

Specifying inline lengths for geospatial columns
Each geometry is stored as a large object (LOB). If the sizes of the geometries that are to be stored in a particular LOB column typically exceed the default inline length for that column, to improve performance, set the inline length for that column to a size that is typical for those geometries. However, because an increased inline length requires additional storage, do not specify an overlarge value in an attempt to cover outliers.
Registering spatial columns
Spatial queries use the spatial reference system associated with the geometry data to construct the shapes for processing. Registering the spatial column improves the description to your data. It also improves query speed, because it allows the spatial reference system to be reused during processing.
Filtering
Identifying relationships between geometries, such as distance, intersections, and containment, requires cartesian joins that typically require extensive calculations. When the tables involved contain large numbers of objects, this can result in long execution times. In such cases, to improve performance, you can use filters to reduce the number of objects that need to be processed.

Parent topic: Db2 Spatial Analytics

Updates to this topic are made in English and are applied to translated versions at a later date. Consequently, the English version of this topic always contains the most recent updates.

See when the translated version of this topic was last updated.
See when the English version of this topic was last updated.