Uploaded image for project: 'Spark'
  1. Spark
  2. SPARK-4386

Parquet file write performance improvement

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.2.0
    • Fix Version/s: 1.2.0
    • Component/s: SQL
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              jimfcarroll Jim Carroll
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: