Performance Evaluation of Yahoo! S4: A First Look

Abstract

Abstract-Processing large data sets has been dominated recently by the map/reduce programming model [3], originally proposed by Google and widely adopted through the Apache Hadoop 1 implementation. Over the years, developers have identified weaknesses of processing data sets in batches as in MapReduce and have proposed alternatives. One such alternative is continuous processing of data streams. This is particularly suitable for applications in online analytics, monitoring, financial data processing and fraud detection that require timely processing of data, making the delay introduced by batch processing highly undesirable. This processing paradigm has led to the development of systems such as Yahoo! S4 [1] and Twitter Storm.2 Yahoo! S4 is a general-purpose, distributed and scalable platform that allows programmers to easily develop applications for processing continuous unbounded streams of data. As these frameworks are quite young and new, there is a need to understand their performance for real time applications and find out the existing issues in terms of scalability, execution time and fault tolerance.We did an empirical evaluation of one application on Yahoo! S4 and focused on the performance in terms of scalability, lost events and fault tolerance. Findings of our analyses can be helpful towards understanding the challenges in developing stream-based data intensive computing tools and thus providing a guideline for the future development.

Energy consumption analysis of data stream processing: a benchmarking approach

“…S4 stream processing platform with a word processor CEP application. The application converts each and every word of a text corpus to numbers and conducts simple filtering and counting to find numbers that can be divided either by 3 or by 11 . Bedini et al modeled the performance of Storm .…”

Processing and Analytics of Big Data Streams with Yahoo!S4

“…to process thousands of search queries per second. A first look and evaluation have been reported in [3], [6].…”

Comparing Distributed Online Stream Processing Systems Considering Fault Tolerance Issues

“…The criterion for selection was strictly the usage, i.e., we choose systems that are currently in production on enterprises that deal with event stream processing. Among the selected are the following: MillWheel [16], S4 [17] [18], Spark Streaming [19] and Storm [20] that are described in next sections.…”