Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Message-ID: <5a427b3c.54dd190a.a1837.2fce@mx.google.com>
MIME-Version: 1.0
To: "user@ignite.apache.org" <user@ignite.apache.org>
Cc: "dev@ignite.apache.org" <dev@ignite.apache.org>
From: Stanislav Lukyanov <stanlukyanov@gmail.com>
Subject: RE: Runtime.availableProcessors() returns hardware's CPU count
 whichis the issue with Ignite in Kubernetes
Date: Tue, 26 Dec 2017 19:39:24 +0300
Importance: normal
In-Reply-To: 
 <CANK09+U4gEi18==Ahcij_QOm6eDc0ocjATcPbRGpBaFab8J+eA@mail.gmail.com>
References: 
 <CANK09+X6Qar=NPiEzheWpf9i4FEPmaNF4RK00+77koCHnSC26A@mail.gmail.com>
 <CAGcMBHgLeWsJad38ar4pwD+0ycyktz+D1TtyRwq=RTbvT4-S3g@mail.gmail.com>
 <CADM=oMa==njvf-x0UzDnxih6Cwk3c3LrLgYQG_R83Vn5RrV7Gg@mail.gmail.com>
 <CAGcMBHitnXuDU+hTsp=g+P0prLTuAKXe7k0dAUSzjBuNsQjE9w@mail.gmail.com>
 <CANK09+U4gEi18==Ahcij_QOm6eDc0ocjATcPbRGpBaFab8J+eA@mail.gmail.com>
Content-Type: multipart/alternative;
	boundary="_42CBA015-8B70-4D13-B2E5-899D2C2367AC_"
archived-at: Tue, 26 Dec 2017 16:39:32 -0000

--_42CBA015-8B70-4D13-B2E5-899D2C2367AC_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

Hi Arseny,

Both OpenJDK and Oracle JDK 8u151 should do.
I=E2=80=99ve checked and it seems that it is indeed about the specific way =
of invoking Docker. By default it doesn=E2=80=99t restrict container to par=
ticular CPUs, but you can make it do that by using `--cpuset-cpus` flag.

Example:
Without cpuset (Docker host has 4 CPUs)
    >docker run -it java-docker bash
    root@8a2cd9d06695:/usr/test# java -version
    openjdk version "1.8.0_151"
    OpenJDK Runtime Environment (build 1.8.0_151-8u151-b12-0ubuntu0.16.04.2=
-b12)
    OpenJDK 64-Bit Server VM (build 25.151-b12, mixed mode)
    root@8a2cd9d06695:/usr/test# jjs
    jjs> print(java.lang.Runtime.runtime.availableProcessors());
    4

With cpuset specifying the first two CPUs
    >docker run -it --cpuset-cpus=3D0,1 java-docker bash
    root@7c2723a9819e:/usr/test# jjs
    jjs> print(java.lang.Runtime.runtime.availableProcessors());
    2

Note also that by using cpuset you change the settings for the whole contai=
ner, not just for the Ignite, so that other Java pools in the same JVM, e.g=
. parallel stream executor, should also work better.

Unfortunately, I=E2=80=99m not familiar with Kubernetes, but the manual [1]=
 says that you can enable the use of cpusets via a static CPU management po=
licy.

Hope that helps,
Stan

[1] https://kubernetes.io/docs/tasks/administer-cluster/cpu-management-poli=
cies/

From: Arseny Kovalchuk
Sent: 26 =D0=B4=D0=B5=D0=BA=D0=B0=D0=B1=D1=80=D1=8F 2017 =D0=B3. 17:37
To: user@ignite.apache.org
Cc: dev@ignite.apache.org
Subject: Re: Runtime.availableProcessors() returns hardware's CPU count whi=
chis the issue with Ignite in Kubernetes

Hi Stanislav.

We use OpenJDK and use Alpine Linux based images. See java version below. I=
n our environment availableProcessors returns CPU's for the host.=C2=A0

Did you mean to try Oracle's JDK 8u151?
arseny@kovalchuka-ubuntu:~/kipod-x$ ku exec ignite-instance-0 -ti bash
bash-4.4# java -version
openjdk version "1.8.0_151"
OpenJDK Runtime Environment (IcedTea 3.6.0) (Alpine 8.151.12-r0)
OpenJDK 64-Bit Server VM (build 25.151-b12, mixed mode)
bash-4.4# jjs
jjs> print(java.lang.Runtime.runtime.availableProcessors());
40
jjs>=C2=A0


=E2=80=8B
Arseny Kovalchuk

Senior Software Engineer at Synesis
skype: arseny.kovalchuk
mobile: +375 (29) 666-16-16
=E2=80=8BLinkedIn Profile=E2=80=8B

On 26 December 2017 at 16:56, Yakov Zhdanov <yzhdanov@gridgain.com> wrote:
Ilya, agree. I like IGNITE_AVAILABLE_CPU more.


Yakov Zhdanov,
www.gridgain.com

2017-12-26 16:36 GMT+03:00 Ilya Lantukh <ilantukh@gridgain.com>:
Hi Yakov,

I think that property IGNITE_NODES_PER_HOST, as you suggested, would be con=
fusing, because users might want to reduce amount of available resources fo=
r ignite node not only because they run multiple nodes per host, but also b=
ecause they run other software. Also, in my opinion all types of system res=
ources (CPU, memory, network) shouldn't be scaled using the same value.

So I'd prefer to have IGNITE_CONCURRENCY_LEVEL or IGNITE_AVAILABLE_PROCESSO=
RS, as it was originally suggested.

On Tue, Dec 26, 2017 at 4:05 PM, Yakov Zhdanov <yzhdanov@apache.org> wrote:
Cross-posting to dev list.

Guys,

Suggestion below makes sense to me. Filed a ticket
https://issues.apache.org/jira/browse/IGNITE-7310

Perhaps, Arseny would like to provide a PR himself ;)

--Yakov

2017-12-26 14:32 GMT+03:00 Arseny Kovalchuk <arseny.kovalchuk@synesis.ru>:

> Hi guys.
>
> Ignite configures all thread pools, selectors, etc. basing on Runtime.ava=
ilableProcessors()
> which seems not correct in containerized environment. In Kubernetes with
> Docker that method returns CPU count of a Node/machine, which is 64 in ou=
r
> particular case. But those 64 CPU and their timings are shared between
> other stuff on the node like other Pods and services. Appropriate value o=
f
> available cores for Pod is usually configured as CPU Resource and estimat=
ed
> basing on different things taking performance into account. General idea,
> if you want to run several Pods on the same node, they all should request
> less resources then the node provides. So, we give 4-8 cores for Ignite
> instance in Kubernetes, but Ignite's thread pools are configured like the=
y
> get all 64 CPUs, and in turn we get a lot of threads for the Pod with 4-8
> cores available.
>
> Now we manually set appropriate values for all available properties which
> relate to thread pools.
>
> Would it be correct to have one environment variable, say
> IGNITE_CONCURRENCY_LEVEL which will be used as a reference value for thos=
e
> configurations and by default equals to Runtime.availableProcessors()?
>
> Thanks.
>
> =E2=80=8B
> Arseny Kovalchuk
>
> Senior Software Engineer at Synesis
> skype: arseny.kovalchuk
> mobile: +375 (29) 666-16-16
> =E2=80=8BLinkedIn Profile <http://www.linkedin.com/in/arsenykovalchuk/en>=
=E2=80=8B
>


--=20
Best regards,
Ilya


--_42CBA015-8B70-4D13-B2E5-899D2C2367AC_--