From user-return-17026-apmail-ignite-user-archive=ignite.apache.org@ignite.apache.org Wed Jan 3 19:39:29 2018 Return-Path: X-Original-To: apmail-ignite-user-archive@minotaur.apache.org Delivered-To: apmail-ignite-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B5277179DB for ; Wed, 3 Jan 2018 19:39:29 +0000 (UTC) Received: (qmail 96159 invoked by uid 500); 3 Jan 2018 19:39:29 -0000 Delivered-To: apmail-ignite-user-archive@ignite.apache.org Received: (qmail 96099 invoked by uid 500); 3 Jan 2018 19:39:29 -0000 Mailing-List: contact user-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.apache.org Delivered-To: mailing list user@ignite.apache.org Received: (qmail 96089 invoked by uid 99); 3 Jan 2018 19:39:29 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Jan 2018 19:39:29 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 85CAF1805A5 for ; Wed, 3 Jan 2018 19:39:28 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.172 X-Spam-Level: ** X-Spam-Status: No, score=2.172 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.972] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id suqzy2FMb3FK for ; Wed, 3 Jan 2018 19:39:27 +0000 (UTC) Received: from n6.nabble.com (n6.nabble.com [162.255.23.37]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 4EFDD5F295 for ; Wed, 3 Jan 2018 19:39:27 +0000 (UTC) Received: from n6.nabble.com (localhost [127.0.0.1]) by n6.nabble.com (Postfix) with ESMTP id 7B8513DB797C for ; Wed, 3 Jan 2018 12:39:26 -0700 (MST) Date: Wed, 3 Jan 2018 12:39:26 -0700 (MST) From: vkulichenko To: user@ignite.apache.org Message-ID: <1515008366502-0.post@n6.nabble.com> In-Reply-To: <1514978824873-0.post@n6.nabble.com> References: <1514891103388-0.post@n6.nabble.com> <1514971097579-0.post@n6.nabble.com> <1514975407035-0.post@n6.nabble.com> <1514978824873-0.post@n6.nabble.com> Subject: Re: Ignite throwing Out Of Memory MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit "Optimal consumption" doesn't mean that you give high ingestion throughput for free. Data streamer is highly optimized for a particular use case and if you try to achieve same results with putAll API, you will likely get worse consumption. If low memory consumption is more important for you than high throughput, then putAll probably suites you better. However, 1GB per node is a VERY low memory allocation for modern hardware and modern applications. I generally recommend to have at least 4GB per node regardless of use case. -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/