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 25A5F200B0F for ; Fri, 17 Jun 2016 12:20:50 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 24219160A61; Fri, 17 Jun 2016 10:20:50 +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 93B1E160A50 for ; Fri, 17 Jun 2016 12:20:49 +0200 (CEST) Received: (qmail 50823 invoked by uid 500); 17 Jun 2016 10:20:48 -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 50813 invoked by uid 99); 17 Jun 2016 10:20:48 -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; Fri, 17 Jun 2016 10:20:48 +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 51D761A0877 for ; Fri, 17 Jun 2016 10:20:48 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.972 X-Spam-Level: X-Spam-Status: No, score=0.972 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972] autolearn=disabled Received: from mx2-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id uY3J1j_7iVPM for ; Fri, 17 Jun 2016 10:20:44 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx2-lw-eu.apache.org (ASF Mail Server at mx2-lw-eu.apache.org) with ESMTP id DE93C5F1F7 for ; Fri, 17 Jun 2016 10:20:43 +0000 (UTC) Received: from malf.nabble.com (unknown [162.253.133.59]) by mbob.nabble.com (Postfix) with ESMTP id A25422A929EB for ; Fri, 17 Jun 2016 03:00:53 -0700 (PDT) Date: Fri, 17 Jun 2016 03:04:41 -0700 (PDT) From: amitpa To: user@ignite.apache.org Message-ID: <1466157881759-5709.post@n6.nabble.com> In-Reply-To: References: <1465901662511-5623.post@n6.nabble.com> <1465919955017-5632.post@n6.nabble.com> <1466075216557-5680.post@n6.nabble.com> <1466094586534-5684.post@n6.nabble.com> Subject: Re: Ignite performance improvements MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Fri, 17 Jun 2016 10:20:50 -0000 yes, I understand that. In production we plan to use that, however one question:- In this case if I use the same key in different transactiosn would it impact performance or it will have no impact? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-performance-improvements-tp5623p5709.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.