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 "Brahma Reddy Battula (JIRA)" <ji...@apache.org> on 2016/02/03 07:16:39 UTC

[jira] [Moved] (MAPREDUCE-6626) Reuse objectMapper instance in MapReduce

     [ https://issues.apache.org/jira/browse/MAPREDUCE-6626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brahma Reddy Battula moved HDFS-9747 to MAPREDUCE-6626:
-------------------------------------------------------

    Affects Version/s:     (was: 2.7.1)
                       2.7.1
          Component/s:     (was: performance)
                       performance
                  Key: MAPREDUCE-6626  (was: HDFS-9747)
              Project: Hadoop Map/Reduce  (was: Hadoop HDFS)

> Reuse objectMapper instance in MapReduce
> ----------------------------------------
>
>                 Key: MAPREDUCE-6626
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6626
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: performance
>    Affects Versions: 2.7.1
>            Reporter: Lin Yiqun
>            Assignee: Lin Yiqun
>         Attachments: MAPREDUCE.001.patch
>
>
> Now in MapReduce, there are some places creating a new ObjectMapper instance every time. In wiki of ObjectMapper, it suggested:
> {code}
> Further: it is beneficial to use just one instance (or small number of instances) for data binding; many optimizations for reuse (of symbol tables, some buffers) depend on ObjectMapper instances being reused. 
> {code}
> http://webcache.googleusercontent.com/search?q=cache:kybMTIJC6F4J:wiki.fasterxml.com/JacksonFAQ+&cd=4&hl=ja&ct=clnk&gl=jp, it's similar to HDFS-9724.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)