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 B6B4C200B2D for ; Thu, 16 Jun 2016 17:58:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B52761602C5; Thu, 16 Jun 2016 15:58:07 +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 D8F7A160A60 for ; Thu, 16 Jun 2016 17:58:06 +0200 (CEST) Received: (qmail 72019 invoked by uid 500); 16 Jun 2016 15:58:06 -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 72006 invoked by uid 99); 16 Jun 2016 15:58:05 -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; Thu, 16 Jun 2016 15:58:05 +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 83D651A007E for ; Thu, 16 Jun 2016 15:58:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.879 X-Spam-Level: * X-Spam-Status: No, score=1.879 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx2-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 dC-785f7fTm2 for ; Thu, 16 Jun 2016 15:58:03 +0000 (UTC) Received: from mail-yw0-f170.google.com (mail-yw0-f170.google.com [209.85.161.170]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTPS id 0BE765F1B3 for ; Thu, 16 Jun 2016 15:58:02 +0000 (UTC) Received: by mail-yw0-f170.google.com with SMTP id g20so47013326ywb.0 for ; Thu, 16 Jun 2016 08:58:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=b0ABSve56GRkTv/Et7j6i6GgnTby6P5Qu1He2krg4NM=; b=XHHUwAfnLPIPxsG8g4R3tTFpLOB/xjS28kSYeFrasVFwapCRxuLdaUPrEARdCNKnBj CQtikWn+m4laT02kEiPsGrDpkSk13vYcGRvDgRRneWPCiLzF9RuUk0R2YvD2CUzGRYBr qAdPROITIKOjT3uQv1aJ4j8a9wG1Nkj8Y/uo2ZhqY9m76TuqdKF1Qm1aqTir3kw8l1em 4/toJUnh0w4z0nGsOhSv82xq4M/Af3gEqNC0xp/JtXe7ENzk8waM1Q26uYR4mdVHof1j PfGZMi5a5ceLL/2z8EiwZOqYcRDMufHjXjckoQQvHdKn4bjXcCJ48kJQvssO55TI5/Dx FnOA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=b0ABSve56GRkTv/Et7j6i6GgnTby6P5Qu1He2krg4NM=; b=b1Bklto00LdfESf0aKJNde7cZLlpgLTdF2yL2t1oQCSRLjBW+z8+NH7EPb8yzovbCd KKV/gCjvxWxVsxOQLVAGK/Z/XanXav0BwaQpf4vi9UCjwrmXHtJgVEL2/brndOHCcqTO LjCNFaFKCRBJP52YnRMe6MMWBP0it2DH3fPvqX5yJbULpC4P/whF2DO8S7EVaMkM9jud 3MD+6PeEQllLxJoIbiZj4GMEvb4JhTZKLdqnx73bidc7x18Qkf8GSBFwZpbfuHNAQA5i vRuBel1STjaflIYsPKqZ960ggT+quKtjjFH99qwtxKEMat+S1/e7PC9H5kPTaX+Wf1gn KsFQ== X-Gm-Message-State: ALyK8tJVMDWgasJm+jUSJu9rCzSg5Aj82p/C4dG7GlBHKu4x4nnnBWoBhLKEq0zVXDjQJMIrctFxsQvpoL0H8g== X-Received: by 10.129.111.5 with SMTP id k5mr3055676ywc.12.1466092682056; Thu, 16 Jun 2016 08:58:02 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.203.71 with HTTP; Thu, 16 Jun 2016 08:58:01 -0700 (PDT) In-Reply-To: <1466075216557-5680.post@n6.nabble.com> References: <1465901662511-5623.post@n6.nabble.com> <1465919955017-5632.post@n6.nabble.com> <1466075216557-5680.post@n6.nabble.com> From: Vladislav Pyatkov Date: Thu, 16 Jun 2016 18:58:01 +0300 Message-ID: Subject: Re: Ignite performance improvements To: user@ignite.apache.org Content-Type: multipart/alternative; boundary=001a11471224859b060535674d8b archived-at: Thu, 16 Jun 2016 15:58:07 -0000 --001a11471224859b060535674d8b Content-Type: text/plain; charset=UTF-8 Hello, Growth loading CPU to 90% may caused by work of GC. For determine this you can get log and analyze log of GC [1]. Also you can use Unix utility for detection causes like dstat or top. In further 50% CPU usage is maybe normal for your case (transaction OPTIMISTIC, READ _COMMITED). You can try to use OPTIMISTIC, SERIALIZABLE transaction, and retry if catch TransactionOptimisticException[2]. [1]: https://apacheignite.readme.io/docs/jvm-and-system-tuning [2]: https://apacheignite.readme.io/docs/transactions On Thu, Jun 16, 2016 at 2:06 PM, amitpa wrote: > My transaction attributes now are OPTIMISTIC, READ _COMMITED. > > Avoided Transaction with the same key. > > Also when there is a lot of data Ignite seems to slow down due to Cache put > and get delays. I see the CPU load increases to 90%. is this due to > resizing > the cache? How can I optimize that? > > Lastly my CPU load is less than 50% when the transactions takes place (4000 > TPS). > > My Access point can take in 1 million per second so its not a bottleneck. > I > am expecting more than 5000 and for transactions to scale as I keep adding > nodes. > > > > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Ignite-performance-improvements-tp5623p5680.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Vladislav Pyatkov --001a11471224859b060535674d8b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello,

Growth loading CPU to= 90% may caused by work of GC. For determine this you can get log and analy= ze log of GC [1]. Also you can use Unix utility for detection causes like d= stat or top.

In further 50% CPU usage is maybe nor= mal for your case (transaction OPTIMISTIC, READ _COMMITED). You can try to = use OPTIMISTIC, SERIALIZABLE transaction, and retry if catch TransactionOpt= imisticException[2].


On Thu, Jun 16, 2016 at 2:06 PM, amitpa = <amitpa@nrifi= ntech.com> wrote:
My trans= action attributes now are OPTIMISTIC, READ _COMMITED.

Avoided Transaction with the same key.

Also when there is a lot of data Ignite seems to slow down due to Cache put=
and get delays. I see the CPU load increases to 90%. is this due to resizin= g
the cache? How can I optimize that?

Lastly my CPU load is less than 50% when the transactions takes place (4000=
TPS).

My Access point can take in 1 million per second so its not a bottleneck.= =C2=A0 I
am expecting more than 5000 and for transactions to scale as I keep adding<= br> nodes.






--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ign= ite-performance-improvements-tp5623p5680.html
Sent from the Apache Ignite Users m= ailing list archive at Nabble.com.



--
=
Vladislav= Pyatkov
--001a11471224859b060535674d8b--