spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Apache Spark (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SPARK-4386) Parquet file write performance improvement
Date Thu, 13 Nov 2014 20:44:33 GMT

    [ https://issues.apache.org/jira/browse/SPARK-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14211271#comment-14211271
] 

Apache Spark commented on SPARK-4386:
-------------------------------------

User 'jimfcarroll' has created a pull request for this issue:
https://github.com/apache/spark/pull/3254

> Parquet file write performance improvement
> ------------------------------------------
>
>                 Key: SPARK-4386
>                 URL: https://issues.apache.org/jira/browse/SPARK-4386
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 1.2.0
>            Reporter: Jim Carroll
>
> If you profile the writing of a Parquet file, the single worst time consuming call inside
of org.apache.spark.sql.parquet.MutableRowWriteSupport.write is actually in the scala.collection.AbstractSequence.size
call. This is because the size call actually ends up COUNTING the elements in a scala.collection.LinearSeqOptimized
("optimized?").
> This doesn't need to be done. "size" is called repeatedly where needed rather than called
once at the top of the method and stored in a 'val'. I have a PR for this.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org


Mime
View raw message