Naveen, 40 caches is quite a lot. It means, that Ignite needs to handle 40 * (number of partitions) files. By default each cache has 1024 partitions. This is quite a lot, and a disk is the bottleneck here. Changing of thread pool sizes won't save you. If you divide your caches into cache groups, then they will share the same partitions, thus number of files will be reduced. You can also try reducing the number of partitions, but it may lead to uneven distribution of data between nodes. Any of these changes will require reloading of the data.
You can record a *dstat* on the host machine to make sure, that disk is the weak place. If its utilization is high, while CPU is not used, then it means, that you need a faster disk. Denis пн, 5 нояб. 2018 г. в 17:10, Naveen <[email protected]>: > Hi Denis > > We have only 40 caches in our cluster. > If we introduce grouping of caches, guess we need to reload the data from > scratch, right ?? > > We do have very powerful machines as part of cluster, they are 128 CPU very > high end boxes and huge resources available, by increasing any of the below > thread pools, can we reduce the cluster activation time. > > System Pool > Public Pool > Striped Pool > Custom Thread Pools > > Thanks > Naveen > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
