<?xml version='1.0' encoding='UTF-8'?>
<OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd">
  <responseDate>2026-04-17T06:43:19Z</responseDate>
  <request metadataPrefix="oai_dc" identifier="oai:meral.edu.mm:recid/5340" verb="GetRecord">https://meral.edu.mm/oai</request>
  <GetRecord>
    <record>
      <header>
        <identifier>oai:meral.edu.mm:recid/5340</identifier>
        <datestamp>2021-12-13T03:12:40Z</datestamp>
        <setSpec>1582963342780:1596102391527</setSpec>
        <setSpec>user-uit</setSpec>
      </header>
      <metadata>
        <oai_dc:dc xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/" xmlns="http://www.w3.org/2001/XMLSchema" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd">
          <dc:title>Efficient Checkpoint Interval for Speculative Execution in MapReduce</dc:title>
          <dc:creator>Naychi Nway Nway</dc:creator>
          <dc:creator>Ei Chaw Htoon</dc:creator>
          <dc:description>The MapReduce has become popular in big data
environment due to its efficient parallel processing.
However, MapReduce still has the problem from job
delay caused by straggling tasks, which prolong job
completion time. In MapReduce framework, although the
existing speculative execution mechanism mitigate
stragglers, its tasks are slower than their original tasks so
this makes job completion time get long when straggling
tasks occur. So, in this paper, a checkpoint mechanism is
proposed in order to increase the efficiency of speculative
execution of MapReduce, and not to prolong job
completion time in case of straggling tasks. However,
MapReduce produces too much intermediate data; as a
result, checkpoint of every intermediate data can still
decrease the performance of MapReduce. So, to avoid this
problem, the proposed system evaluates checkpoint
interval in order to reduce job completion time in case of
stragglers. Then, the proposed system defines stragglers
using LATE scheduler. The proposed checkpoint interval
is based on five parameters: expected job completion time
without checkpointing, checkpoint overhead time, rework
time, down time and restart time. Experimental results
show that the proposed system leads to less completion
time, rework time and checkpoint overhead.</dc:description>
          <dc:date>2018-11-01</dc:date>
          <dc:identifier>http://hdl.handle.net/20.500.12678/0000005340</dc:identifier>
          <dc:identifier>https://meral.edu.mm/records/5340</dc:identifier>
        </oai_dc:dc>
      </metadata>
    </record>
  </GetRecord>
</OAI-PMH>
