Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Message-ID: <5a424efe.170f190a.e630d.6a70@mx.google.com>
MIME-Version: 1.0
To: "dev@ignite.apache.org" <dev@ignite.apache.org>,
	"user@ignite.apache.org" <user@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 16:30:38 +0300
Importance: normal
In-Reply-To: 
 <CAGcMBHgLeWsJad38ar4pwD+0ycyktz+D1TtyRwq=RTbvT4-S3g@mail.gmail.com>
References: 
 <CANK09+X6Qar=NPiEzheWpf9i4FEPmaNF4RK00+77koCHnSC26A@mail.gmail.com>
 <CAGcMBHgLeWsJad38ar4pwD+0ycyktz+D1TtyRwq=RTbvT4-S3g@mail.gmail.com>
Content-Type: multipart/alternative;
	boundary="_3C8E4489-3650-490C-A5D0-52A75BF4318A_"
archived-at: Tue, 26 Dec 2017 13:30:51 -0000

--_3C8E4489-3650-490C-A5D0-52A75BF4318A_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

Hi Arseny,

This behavior of the `Runtime.availableProcessors()` is actually a recogniz=
ed issue of the Hotspot, see [1]. It was fixed not that long ago for JDK 9 =
and 8uX, and I can see correct values returned in my Docker environment wit=
h JDK 8u151, although I believe it depends on a specific way a container is=
 configured.

Which Java version do you use? Can you try your code on JDK 8u151?

BTW see also [2] and [3] on more stuff to be fixed in JDK for better contai=
ner support.

Thanks,
Stan

[1] https://bugs.openjdk.java.net/browse/JDK-6515172
[2] https://bugs.openjdk.java.net/browse/JDK-8146115
[3] https://bugs.openjdk.java.net/browse/JDK-8182070


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

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
>


--_3C8E4489-3650-490C-A5D0-52A75BF4318A_--