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

Posted to issues@spark.apache.org by "Jim Carroll (JIRA)" <ji...@apache.org> on 2014/11/13 21:26:34 UTC

[jira] [Created] (SPARK-4386) Parquet file write performance improvement

Jim Carroll created SPARK-4386:
----------------------------------

             Summary: 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