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 5BAF6200CCC for ; Fri, 7 Jul 2017 05:29:25 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 5A269168081; Fri, 7 Jul 2017 03:29:25 +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 7842D168074 for ; Fri, 7 Jul 2017 05:29:24 +0200 (CEST) Received: (qmail 24435 invoked by uid 500); 7 Jul 2017 03:29:22 -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 24425 invoked by uid 99); 7 Jul 2017 03:29:22 -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; Fri, 07 Jul 2017 03:29:22 +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 EB446181944 for ; Fri, 7 Jul 2017 03:29:21 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.679 X-Spam-Level: * X-Spam-Status: No, score=1.679 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_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 6y1NVRqs9V17 for ; Fri, 7 Jul 2017 03:29:20 +0000 (UTC) Received: from mail-it0-f50.google.com (mail-it0-f50.google.com [209.85.214.50]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 59BDC5FB32 for ; Fri, 7 Jul 2017 03:29:20 +0000 (UTC) Received: by mail-it0-f50.google.com with SMTP id 188so1101991itx.0 for ; Thu, 06 Jul 2017 20:29:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=1+8wP+D1lzVpDJ5zKdFLmZ/DURp6HhGooqR7yhh7IMo=; b=nxsU9OIpy/FIG75n18oBRfKRzJpejrfYL8ZIHQ1ueQ0J6sotmPnyBkjDNY1T+xcSrD hFahOPdIJIxH9a8HdaEKS3pzTgfMjg++dQCV9TffvuakkBN8u7VvWdktyWH+z4LSPQMa mqCvxjVM96zvI8oXNhGqwzKPeJkWTCS/JeYslbBOq2CSscAD3alpc4cNHiPsTyKJkort Z2Nmkab/YWSs5I9Cqun4/WdAuUXEf10s2lDjCQPvfMP2QNuhyS0Ax7D2wVp4BNEZS82e ToWvrh4/I/mlusBEu5/qtFYg81zOnFb6K0mVX91pWRPQ+XRpWVJIbgnRRZV0qLX3OZpj lx7A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=1+8wP+D1lzVpDJ5zKdFLmZ/DURp6HhGooqR7yhh7IMo=; b=sPIAtbqj89Mpt/LJVaRFDUBjQE1IU1yR6NlyFS74adIqjFAllqquvmk08JCscaPcWr S27ZSPNKVPpjIjONOiMJ0ZNWX7R4r0gF+/jvUyoX3JURfDujBmzi4R6P5E4i/ap+ufxc R+HR9J2JK9VE8k8W1IUoy4L+uASyIqgY3rcQyeiqJPCtpugTyEjCxuRzMqJ6+3M0Zvz5 1tWMUgrfH6aNrFjkLboMxekfWAyPOFR5Wsp13WgOHtu68mP2sxzE6r7mzlYt1ONG+hJR VXnCENFFgVAFXrpTa/ipqTmD5mMbNbZaZsSyN+D+g9COb5fG73Z7RL/WwQHppchlDx4n +s8w== X-Gm-Message-State: AIVw111LqSPbIqGQsgHnpdzKiKqh7pH7yORi/+wMIduhgOYzAyAZvzbr v8PH5PLQL9fe5CWM2TVbl6T/RIo+7g== X-Received: by 10.36.74.209 with SMTP id k200mr1022055itb.51.1499398159367; Thu, 06 Jul 2017 20:29:19 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.13.213 with HTTP; Thu, 6 Jul 2017 20:28:38 -0700 (PDT) In-Reply-To: References: From: Anil Date: Fri, 7 Jul 2017 08:58:38 +0530 Message-ID: Subject: Re: High heap on ignite client To: user@ignite.apache.org Content-Type: multipart/alternative; boundary="001a114044c6aa939d0553b1d6cc" archived-at: Fri, 07 Jul 2017 03:29:25 -0000 --001a114044c6aa939d0553b1d6cc Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Alex, Thanks. i have changed the swapiness to avoid sys time > user time. and did test but no luck. What do you mean by "apps/containers running on same physical machine" ? You mean on kube instance ? if yes, yes there are number of services/containers running on same kube cluster/instance. Ignite client need high CPU ? Thanks, Anil On 6 July 2017 at 17:39, afedotov wrote: > Hi, > > I've taken a look at the logs. > I don't see huge heap consumption but from the GC log for node1 I can see > that in a couple of GCs real time is greater than user and sys time, as > well as > in some cases sys time is higher than the user time. Taking into account > that you are running kubernetes and probably in a virtual environment, I > suspect that > overselling takes place here. Please check if there are other > apps/containers running on the same physical machine. > > Kind regards, > Alex. > > On Thu, Jul 6, 2017 at 7:23 AM, Anil [via Apache Ignite Users] <[hidden > email] > wrote= : > >> Hi Alex, >> >> Did you get a chance to look into it ? thanks. >> >> Regards, >> Anil >> >> >> >> ------------------------------ >> If you reply to this email, your message will be added to the discussion >> below: >> http://apache-ignite-users.70518.x6.nabble.com/High-heap-on- >> ignite-client-tp13594p14372.html >> To start a new topic under Apache Ignite Users, email [hidden email] >> >> To unsubscribe from Apache Ignite Users, click here. >> NAML >> >> > > > ------------------------------ > View this message in context: Re: High heap on ignite client > > Sent from the Apache Ignite Users mailing list archive > at Nabble.com. > --001a114044c6aa939d0553b1d6cc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Alex,

Thanks.

i have changed the swapiness to avoid sys time > user time. and did t= est but no luck.

What do you mean by "apps/co= ntainers running on same physical machine" ?=C2=A0

You mean on kube instance ? if yes, yes there are number of services/= containers running on same kube cluster/instance.

= Ignite client need high CPU ?=C2=A0

Thanks,
<= div>Anil

On = 6 July 2017 at 17:39, afedotov <alexander.fedotoff@gmail.com> wrote:
Hi,<= br>
I've taken a look at the logs.=C2=A0
I don't see huge hea= p consumption but from the GC log for node1 I can see that in a couple of G= Cs real time is greater than user and sys time, as well as
in some cases= sys time is higher than the user time. Taking into account that you are ru= nning kubernetes and probably in a virtual environment, I suspect that
= overselling takes place here. Please check if there are other apps/containe= rs running on the same physical machine.

Kind regards,
Alex.

On Thu, Jul 6, 2017 at 7:23 AM, Anil [via Ap= ache Ignite Users] <[hidden email]> wrote:
Hi Alex,

Did you get a chance to= look into it ? thanks.

Regards,
= Anil

=09 =09 =09

If you reply to this email, your message = will be added to the discussion below:
http://apache-ignite-users.70518.x6.nabble.com/High-h= eap-on-ignite-client-tp13594p14372.html
To start a new topic under Apache Ignite Users, email [hidden email]
To unsubscribe from Apache Ignite Users, click here.
NAML

=09 =09 =09
View this message in context: Re: High heap on ignite client
Sent from the Apache Ignite Users mailing list archive at Nabble.com= .

--001a114044c6aa939d0553b1d6cc--