[
https://issues.apache.org/jira/browse/MAPREDUCE-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280391#comment-13280391
]
Hudson commented on MAPREDUCE-4274:
-----------------------------------
Integrated in Hadoop-Hdfs-trunk-Commit #2350 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/2350/])
MAPREDUCE-4274 MapOutputBuffer should use native byte order for kvmeta.
(todd via bobby) (Revision 1341151)
Result = SUCCESS
bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1341151
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/MapTask.java
> MapOutputBuffer should use native byte order for kvmeta
> -------------------------------------------------------
>
> Key: MAPREDUCE-4274
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4274
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: performance, task
> Affects Versions: 2.0.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Minor
> Fix For: 2.0.0, 3.0.0
>
> Attachments: mapreduce-4274.txt
>
>
> I don't have a benchmark to support this, but this should give a small CPU
> improvement on the map output buffer: currently, we create {{kvmeta}} as
> {{ByteBuffer.wrap(kvbuffer).asIntBuffer()}}. According to the javadocs, the
> resulting int buffer will inherit its byte order from the ByteBuffer it comes
> from, and the byte buffer defaults to BIG_ENDIAN. Thus, all of our int access
> to/from the buffer will require byte-swapping.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
