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 "Akira AJISAKA (JIRA)" <ji...@apache.org> on 2016/02/09 19:04:18 UTC

[jira] [Updated] (MAPREDUCE-6626) Reuse ObjectMapper instance in MapReduce

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

Akira AJISAKA updated MAPREDUCE-6626:
-------------------------------------
        Priority: Minor  (was: Major)
    Hadoop Flags: Reviewed
         Summary: Reuse ObjectMapper instance in MapReduce  (was: Reuse objectMapper instance in MapReduce)

> 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
>            Priority: Minor
>         Attachments: MAPREDUCE-6626.002.patch, MAPREDUCE-6626.003.patch, MAPREDUCE-6626.004.patch, 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)