[
https://issues.apache.org/jira/browse/SPARK-8135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14575410#comment-14575410
]
Sandy Ryza commented on SPARK-8135:
-----------------------------------
Your question made me think about the fact that, whether or not we go through
ObjectWritable, we're still going to end up calling the default Configuration
constructor when SerializableWritable wraps a Configuration. I think this is
undesirable for the reasons outlined above.
What do you think about adding a SerializableConfiguration class that
instantiates a Configuration with loadDefaults = false?
Regarding your question, I think we could get away with that. Is there an
advantage though? I think it would probably be more code.
> In SerializableWritable, don't load defaults when instantiating Configuration
> -----------------------------------------------------------------------------
>
> Key: SPARK-8135
> URL: https://issues.apache.org/jira/browse/SPARK-8135
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
>
> Calling "new Configuration()" is an expensive operation because it loads any
> Hadoop configuration XMLs from disk.
> In SerializableWritable, we call new Configuration needlessly when
> instantiating an ObjectWritable. The ObjectWritable only needs the
> Configuration for its class cache, not for any Hadoop properties that might
> be in XML files, so it should be ok to call new Configuration with
> loadDefaults = false.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
