Performance comparison of three spark-based implementations of parallel entity resolution

3Citations
Citations of this article
2Readers
Mendeley users who have this article in their library.
Get full text

Abstract

During the last decade, several big data processing frameworks have emerged enabling users to analyze large scale data with ease. With the help of those frameworks, people are easier to manage distributed programming, failures and data partitioning issues. Entity Resolution is a typical application that requires big data processing frameworks, since its time complexity increases quadratically with the input data. In recent years Apache Spark has become popular as a big data framework providing a flexible programming model that supports in-memory computation. Spark offers three APIs: RDDs, which gives users core low-level data access, and high-level APIs like DataFrame and Dataset, which are part of the Spark SQL library and undergo a process of query optimization. Stemming from their different features, the choice of API can be expected to have an influence on the resulting performance of applications. However, few studies offer experimental measures to characterize the effect of such distinctions. In this paper we evaluate the performance impact of such choices for the specific application of parallel entity resolution under two different scenarios, with the goal to offer practical guidelines for developers.

Cite

CITATION STYLE

APA

Chen, X., Rapuru, K., Durand, G. C., Schallehn, E., & Saake, G. (2018). Performance comparison of three spark-based implementations of parallel entity resolution. In Communications in Computer and Information Science (Vol. 903, pp. 76–87). Springer Verlag. https://doi.org/10.1007/978-3-319-99133-7_6

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free