You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2018/06/20 18:57:00 UTC

[jira] [Created] (HADOOP-15550) Avoid static initialization of ObjectMappers

Todd Lipcon created HADOOP-15550:
------------------------------------

             Summary: Avoid static initialization of ObjectMappers
                 Key: HADOOP-15550
                 URL: https://issues.apache.org/jira/browse/HADOOP-15550
             Project: Hadoop Common
          Issue Type: Bug
          Components: performance
    Affects Versions: 3.2.0
            Reporter: Todd Lipcon
            Assignee: Todd Lipcon


Various classes statically initialize an ObjectMapper READER instance. This ends up doing a bunch of class-loading of Jackson libraries that can add up to a fair amount of CPU, even if the reader ends up not being used. This is particularly the case with WebHdfsFileSystem, which is class-loaded by a serviceloader even when unused in a particular job. We should lazy-init these members instead of doing so as a static class member.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org