Reverse-k-Nearest-Neighbor join processing

  • Authors:
  • Tobias Emrich;Hans-Peter Kriegel;Peer Kröger;Johannes Niedermayer;Matthias Renz;Andreas Züfle

  • Affiliations:
  • Institute for Informatics, Ludwig-Maximilians-Universität München, Germany;Institute for Informatics, Ludwig-Maximilians-Universität München, Germany;Institute for Informatics, Ludwig-Maximilians-Universität München, Germany;Institute for Informatics, Ludwig-Maximilians-Universität München, Germany;Institute for Informatics, Ludwig-Maximilians-Universität München, Germany;Institute for Informatics, Ludwig-Maximilians-Universität München, Germany

  • Venue:
  • SSTD'13 Proceedings of the 13th international conference on Advances in Spatial and Temporal Databases
  • Year:
  • 2013

Quantified Score

Hi-index 0.00

Visualization

Abstract

A reverse k-nearest neighbour (RkNN) query determines the objects from a database that have the query as one of their k-nearest neighbors. Processing such a query has received plenty of attention in research. However, the effect of running multiple RkNN queries at once (join) or within a short time interval (bulk/group query) has only received little attention so far. In this paper, we analyze different types of RkNN joins and discuss possible solutions for solving the non-trivial variants of this problem, including self and mutual pruning strategies. The results indicate that even with a moderate number of query objects (|R|≈0.0007|S|), the performance (CPU) of the state-of-the-art mutual pruning based RkNN-queries deteriorates and hence algorithms based on self pruning without precomputation produce better results. During an extensive performance analysis we provide evaluation results showing the IO and CPU performance of the compared algorithms for a wide range of different setups and suggest appropriate query algorithms for specific scenarios.