You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/17 23:54:06 UTC
[jira] [Resolved] (MAPREDUCE-283) We should reuse key and value
objects in the MultithreadedMapRunner.
[ https://issues.apache.org/jira/browse/MAPREDUCE-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer resolved MAPREDUCE-283.
----------------------------------------
Resolution: Incomplete
Closing this as stale.
> We should reuse key and value objects in the MultithreadedMapRunner.
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-283
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-283
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Reporter: Owen O'Malley
>
> Currently, each key/value pair read from the record reader is allocated a new a key and value. It would be better if it had a pool of key/value pairs that were reused. I'm picturing something like:
> BlockingQueue<KeyValuePair> empties;
> BlockingQueue<KeyValuePair> newInputs;
> the record reader thread would take a KeyValuePair from the empties queue, read into it using the RecordReader, and put it on the newInputs queue.
> The work threads would read from newInputs, process the key and value and put the processed objects on the empties queue. The initialization would put the desired number of key-value pairs on the empties queue to start it off.
--
This message was sent by Atlassian JIRA
(v6.2#6252)