Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id D8191200C52 for ; Mon, 10 Apr 2017 09:29:23 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D6969160B99; Mon, 10 Apr 2017 07:29:23 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 29B6C160B85 for ; Mon, 10 Apr 2017 09:29:23 +0200 (CEST) Received: (qmail 47945 invoked by uid 500); 10 Apr 2017 07:29:22 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 47557 invoked by uid 99); 10 Apr 2017 07:29:20 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Apr 2017 07:29:20 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id D66621A0946 for ; Mon, 10 Apr 2017 07:29:16 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.986 X-Spam-Level: *** X-Spam-Status: No, score=3.986 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, KAM_NUMSUBJECT=0.5, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972, URI_HEX=1.313] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id LiKbWbb9EZ83 for ; Mon, 10 Apr 2017 07:29:16 +0000 (UTC) Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 0AEAA5FDB4 for ; Mon, 10 Apr 2017 07:29:16 +0000 (UTC) Received: from mjoe.nabble.com (unknown [162.253.133.57]) by mwork.nabble.com (Postfix) with ESMTP id 5A8CB38C9662C for ; Mon, 10 Apr 2017 00:29:15 -0700 (MST) Date: Mon, 10 Apr 2017 00:19:49 -0700 (PDT) From: daradurvs To: dev@ignite.apache.org Message-ID: <1491808789290-16317.post@n4.nabble.com> In-Reply-To: References: Subject: Re: Data compression in Ignite 2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Mon, 10 Apr 2017 07:29:24 -0000 Hi Igniters! I am interested in this task. Provide some kind of pluggable compression SPI support I developed a solution on BinaryMarshaller-level, but reviewer has rejected it. Let's continue discussion of task goals and solution design. As I understood that, the main goal of this task is to store data in compressed form. This is what I need from Ignite as its user. Compression provides economy on servers. We can store more data on same servers at the cost of increasing CPU utilization. I'm researching a possibility of implementation of compression at the cache-level. Any thoughts? -- Best regards, Vyacheslav -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Data-compression-in-Ignite-2-0-tp10099p16317.html Sent from the Apache Ignite Developers mailing list archive at Nabble.com.