During the mapper or reducer task execution the following steps take place:

• Perl script is executed in the current directory, ie. in the directory where the job was executed / submitted from.
• Mapper/Reducer object is constructed.
• Method setup($self, $context) is called on this object. The $context can be already used to produce (key, value) pairs or increment counters.
• Method map or reduce is called for all input values.
• Method cleanup($self, $context) is called after all (key, value) pairs of this task are processed. Again, the $context can be used to produce (key, value) pairs or increment counters.
• Perl script finishes.

The setup and cleanup methods are very useful for initialization and cleanup of the tasks.

Please note that complex initialization should not be performed during construction of Mapper and Reducer objects, as these are constructed every time the script is executed.

Improve the wc-without-combiner.pl script by manually combining the results in the Mapper – create a hash of word occurrences, fill it during the map calls and output the (key, value) pairs in cleanup method.

Then measure the improvement.

Solution.pl

As you have seen, the combiners are not efficient when using the Perl API. This is a problem of Perl API – reading and writing the (key, value) pairs is relatively slow and a combiner does not help – it in fact increases the number of (key, value) pairs that need to be read/written.

This is even more obvious with larger input data:

For comparison, here are times of Java solutions:

Using the combiner is beneficial, although manually combining the word occurences in mapper manually is still faster.