Mailing-List: contact reviews-help@spark.apache.org; run by ezmlm
Precedence: bulk
From: tgravescs <git@git.apache.org>
To: reviews@spark.apache.org
Reply-To: reviews@spark.apache.org
References: <git-pr-17303-spark@git.apache.org>
In-Reply-To: <git-pr-17303-spark@git.apache.org>
Subject: [GitHub] spark issue #17303: [SPARK-19112][CORE] add codec for ZStandard
Content-Type: text/plain
Message-Id: <20170315134343.6DC79DFE1E@git1-us-west.apache.org>
Date: Wed, 15 Mar 2017 13:43:43 +0000 (UTC)
archived-at: Wed, 15 Mar 2017 13:43:45 -0000

Github user tgravescs commented on the issue:

    https://github.com/apache/spark/pull/17303
  
    this should not be needed just to use to write to hdfs.  The regular hadoop input/output type formats have support for it if you are using the right version (I think hadoop 2.8).
    
    This seems to be adding the support to the spark.io.compression.codec for internal compression.  From what I've heard zstd is better then the other codecs since it gives Gzip level Compression with Lz4 level CPU usage.  So if you have  a job that had a ton of intermediate data or was causing network issues you may want to use ztsd to get the gzip compression levels without much cpu penalty.
    
     @dongjinleekr  It doesn't looks like you ran any manual tests on a real cluster?  It would be nice to have some basic performance/compression numbers to show it actually working.    Are you planning on actually using zstd in your spark deployment?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

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