GridKernalContextImpl.isDaemon is calling System.Properties frequently

Hello, I was performing some tuning using JFR with our application, and I have found that in many of the cache get it makes a lot of calls to get System Properties, which is a synchronized call. Upon further examination of the code I have found that we can potentially optimized the code to

RE: Configuring Ignite Thread Pool's Core thread count/max thread count/etc

object, similar to my proposal 2 –would that be better? From: Ilya Kasnacheev Sent: Thursday, February 27, 2020 6:05 PM To: Sunny Chan, CLSA Cc: dev Subject: Re: Configuring Ignite Thread Pool's Core thread count/max thread count/etc Hello! My suggestion is to use

RE: Configuring Ignite Thread Pool's Core thread count/max thread count/etc

count/max thread count/etc Hello! We recommend exposing IgniteConfiguration for user to modify. You never know in advance what kind of tuning will be needed, and don't want to play chinese whispers game with your users. Regards, -- Ilya Kasnacheev ср, 26 февр. 2020 г. в 13:07, Sunny Chan, CLSA

Configuring Ignite Thread Pool's Core thread count/max thread count/etc

Hello, We are running Ignite cluster on bare metal on a relatively high core count machine (4x10 cores 20 threads), and looking some of the thread pool initialization code: (IgnitionEx.java) sysExecSvc = new IgniteThreadPoolExecutor( "sys",

RE: Log level changes in GridCacheWriteBehindStore.updateStore

Sorry for taking so long, but it has dropped down my priority list :( I have now provided a github pull request for the logging changes I would like to make. Please review and let me know whether my patch is acceptable -Original Message- From: Sunny Chan, CLSA Sent: Friday, August 30

RE: Log level changes in GridCacheWriteBehindStore.updateStore

Hello! I think you should go ahead and create a JIRA ticket about it, then someone (or even you) can check it and fix it. Regards, -- Ilya Kasnacheev пн, 26 авг. 2019 г. в 09:17, Sunny Chan, CLSA : > Hello, > > > > In the GridCacheWriteBehindStore > <https://urldefense.

Log level changes in GridCacheWriteBehindStore.updateStore

Hello, In the GridCacheWriteBehindStore, when the updateStore failed to write to underlying store, it

Null check removal in IGNITE-5779

Hello, In Ignite-5779 patch, CassandraSessionImpl.java line 289 a null check for row has been removed (before the change:

RE: IGNITE-6252 patch

. will review the changes as soon as prolonged holidays are over. — Denis > On Jan 2, 2018, at 5:24 PM, Sunny Chan, CLSA <sunny.c...@clsa.com> wrote: > > Hello, > > I have replied to the comment in November and I am okay with your updated > patch – what do I need to

RE: IGNITE-6252 patch

Hello, I have replied to the comment in November and I am okay with your updated patch – what do I need to do to move this forward? From: Nikolai Tikhonov [mailto:ntikho...@apache.org] Sent: Tuesday, October 31, 2017 11:50 PM To: dev@ignite.apache.org; Sunny Chan, CLSA Subject: Re: IGNITE-6252

RE: [jira] [Created] (IGNITE-7083) Reduce memory usage of CachePartitionFullCountersMap

I have created a pull request for my proposed change. https://github.com/apache/ignite/pull/3152 -Original Message- From: Denis Magda [mailto:dma...@apache.org] Sent: Saturday, December 02, 2017 3:10 AM To: dev@ignite.apache.org; Semen Boikov; Alexey Goncharuk Subject: Fwd: [jira]

RE: IGNITE-6252 patch

I have reviewed and it looks good. From: Nikolai Tikhonov [mailto:ntikho...@apache.org] Sent: Tuesday, October 31, 2017 11:50 PM To: dev@ignite.apache.org; Sunny Chan, CLSA Subject: Re: IGNITE-6252 patch Hello, Thank you for your contribution! I've reviewed your changes and left comment

IGNITE-6252 patch

Hello, During our testing we have found an issue and I have raised a JIRA ticket https://issues.apache.org/jira/browse/IGNITE-6252. I have also provided a patch that would fix the issue. Could someone take a look and see whether the patch is acceptable? Thanks. The content of this