Experimental evaluation of memory configurations of Hadoop in Docker environments

Xueyuan Wang, Brian Lee, Yuansong Qiao

    Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

    8 Citations (Scopus)

    Abstract

    Hadoop is widely used in these days for big data analytics. Docker, a new container technology, is hot nowadays, and is the new QuickStart option for Apache Hadoop. It is a trend to build Hadoop cluster in Docker environments in clouds or clusters. However, how to make better use of hardware resources and improve Hadoop performance in Docker environments is a challenge for users. In this paper we study memory configurations of Hadoop in Docker environments, and analyse the performance of Hadoop while altering Hadoop's memory configurations. We select two different applications (a CPU-intensive application - WordCount and a memory-intensive application - TeraSort) and measure their resource usages in terms of CPU and memory footprint. Extensive tests have been executed, the test results show that appropriate customization of memory configurations improves performance compared to the default memory parameter settings.

    Original languageEnglish
    Title of host publication2016 27th Irish Signals and Systems Conference, ISSC 2016
    PublisherInstitute of Electrical and Electronics Engineers Inc.
    ISBN (Electronic)9781509034093
    DOIs
    Publication statusPublished - 1 Aug 2016
    Event27th Irish Signals and Systems Conference, ISSC 2016 - Londonderry, United Kingdom
    Duration: 21 Jun 201622 Jun 2016

    Publication series

    Name2016 27th Irish Signals and Systems Conference, ISSC 2016

    Conference

    Conference27th Irish Signals and Systems Conference, ISSC 2016
    Country/TerritoryUnited Kingdom
    CityLondonderry
    Period21/06/1622/06/16

    Keywords

    • Docker
    • Hadoop
    • configuration
    • memory

    Fingerprint

    Dive into the research topics of 'Experimental evaluation of memory configurations of Hadoop in Docker environments'. Together they form a unique fingerprint.

    Cite this