Hi Naveen and Andrey, We've recently done major optimization https://issues.apache.org/jira/browse/IGNITE-9420 that will speed-up activation time in your case. Iteration over WAL now happens only on a node start-up, so it will not affect activation anymore. Partitions state restoring (which is the slowest part of the activation phase as I see in the first message in the thread) was also optimized. Now it is performed in parallel for each of available cache groups. Parallelism level of that operation is controlled by System Pool size. If you have enough CPU cores on your machines (more than the number of configured cache groups) you can adjust System pool size and your activation time will be significantly improved.
вт, 6 нояб. 2018 г. в 17:23, Naveen <[email protected]>: > Hi Denis > > We have already reduced the partition to 128, after which activation time > has come down a bit. > > You were saying that, by reducing the partitions, it may lead to uneven > distribution of data between nodes. Isn't it the same when we go for cache > groups, group of caches will use the same resources /partitions, so here > also resource contention may be there right ?? here also same set of > partitions used by group of caches ? > If we use cache group, partition size may grow very high since all the > caches belong to that group will use the same set of partitions, does it > have any negative effect on the cluster performance ?? > > > > Thanks > Naveen > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
