Changes between Version 6 and Version 7 of PerformanceEnhancements


Ignore:
Timestamp:
Mar 5, 2010, 7:32:25 AM (14 years ago)
Author:
simonp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PerformanceEnhancements

    v6 v7  
    4343      * multiple threads to schedule documents that need to be written to the index without blocking
    4444   
    45  * Speeding up spatial indexing: !GeoNetwork uses a shapefile to hold spatial extents for searches that contain spatial queries eg. touch, intersect, contains, overlap etc. At present only the CSW service uses the spatial index for these queries, the web search interface uses boxes and !Lucene.
     45 * Speeding up spatial indexing using PostGIS: !GeoNetwork uses a shapefile to hold spatial extents for searches that contain spatial queries eg. touch, intersect, contains, overlap etc. At present only the CSW service uses the spatial index for these queries, the web search interface uses boxes and !Lucene. The spatial index needs to be maintained when records are added and deleted through import, harvesting, massive delete etc. Unfortunately the shapefile is not efficient for this purpose as the number of records in the catalog goes over 40,000 odd. In particular as the mechanism for deleting extents from the shapefile uses an attribute of the extent and these are not indexable meaning that there is a considerable cost for maintenance operations on the shapefile.
    4646
    4747=== Backwards Compatibility Issues ===