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 077F4200BD1 for ; Mon, 28 Nov 2016 22:41:32 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 06650160B0D; Mon, 28 Nov 2016 21:41:32 +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 50128160B00 for ; Mon, 28 Nov 2016 22:41:31 +0100 (CET) Received: (qmail 69691 invoked by uid 500); 28 Nov 2016 21:41:30 -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 69681 invoked by uid 99); 28 Nov 2016 21:41:30 -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; Mon, 28 Nov 2016 21:41:30 +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 1D367180254 for ; Mon, 28 Nov 2016 21:41:30 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.174 X-Spam-Level: ** X-Spam-Status: No, score=2.174 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972, URIBL_BLOCKED=0.001] 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 LY9rlU87xXMS for ; Mon, 28 Nov 2016 21:41:27 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 1894B5F54E for ; Mon, 28 Nov 2016 21:41:27 +0000 (UTC) Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37]) by mbob.nabble.com (Postfix) with ESMTP id C70E336DDFA7 for ; Mon, 28 Nov 2016 13:30:00 -0800 (PST) Date: Mon, 28 Nov 2016 14:41:25 -0700 (MST) From: vkulichenko To: user@ignite.apache.org Message-ID: <1480369285942-9237.post@n6.nabble.com> In-Reply-To: <1480318050486-9208.post@n6.nabble.com> References: <1480318050486-9208.post@n6.nabble.com> Subject: Re: AtomicSequence not performing well with 2 nodes cluster set up MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Mon, 28 Nov 2016 21:41:32 -0000 Hi, First of all, if you don't need ranges, you should use IgniteAtomicLong instead of the sequence. But you should keep in mind that updating the atomic long is actually the same as updating the same cache entry, so you acquire an exclusive write lock each time you do this. That's why sequence is much faster - it doesn't do any distributed operations within a reserved range. If you need performance, you should revisit your approach and try using sequences with larger ranges. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/AtomicSequence-not-performing-well-with-2-nodes-cluster-set-up-tp9208p9237.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.