Hi David, Described behaviour (when too much time is spend on locks) was fixed in Ignite 2.5 by 3 or 4 optimization changes.
IMO release will be published soon,so new Ignite vesion should get performance boost in this case. Yes, 'times 4' should be removed from the doc https://apacheignite.readme.io/docs/memory-configuration#section-global-configuration-parameters Sincerely, Dmitriy Pavlov вт, 29 мая 2018 г. в 5:42, Dave Harvey <[email protected]>: > It does appear that if the global concurrentLevel is not set, that it > defaults to # CPUs not 4 * # CPUs as documented here > > https://apacheignite.readme.io/docs/memory-configuration#section-global-configuration-parameters > > > private long[] calculateFragmentSizes(int concLvl, long cacheSize, long > chpBufSize) { > if (concLvl < 2) > concLvl = Runtime.getRuntime().availableProcessors(); > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
