Dynamic routing of data stream tuples among parallel query plan running on multi-core processors

  • Authors:
  • Ali A. Safaei;Ali Sharifrazavian;Mohsen Sharifi;Mostafa S. Haghjoo

  • Affiliations:
  • School of Computer Engineering, Iran University of Science and Technology, Tehran, Iran;School of Computer Engineering and IT, Sharif University of Technology, Tehran, Iran;School of Computer Engineering, Iran University of Science and Technology, Tehran, Iran;School of Computer Engineering, Iran University of Science and Technology, Tehran, Iran

  • Venue:
  • Distributed and Parallel Databases
  • Year:
  • 2012

Quantified Score

Hi-index 0.00

Visualization

Abstract

In this paper, a method for fast processing of data stream tuples in parallel execution of continuous queries over a multiprocessing environment is proposed. A copy of the query plan is assigned to each of processing units in the multiprocessing environment. Dynamic and continuous routing of input data stream tuples among the graph constructed by these copies (called the Query Mega Graph) for each input tuple determines that, after getting processed by each processing unit (e.g., processor), to which next processor it should be forwarded. Selection of the proper next processor is performed such that the destination processor imposes the minimum tuple latency to the corresponding tuple, among all of the alternative processors. The tuple latency is derived from processing, buffering and communication time delay which varies in different practical parallel systems.Parallel system architectures that would be suitable as the desired multiprocessing environment for employing the proposed Dynamic Tuple Routing (DTR) method are considered and analyzed. Also, practical challenges and issues for the proper parallel underlying system are discussed. Implementation of the desired parallel system on multi-core systems is provided and used for evaluating the proposed DTR method. Evaluation results show that the proposed DTR method outperforms similar method such as the Eddies in terms of tuple latency, throughput and tuple loss.