Thread pool for partition aware operations

[hitendrapratap <hi...@target.com>]

Is there any separate thread pool for partition aware operations (Affinity
Key IgniteCallable, Entry Processor)? If its there then how we can configure
it?Is there any consequences of increasing the same.

Is there any separate thread pool for normal operations like GET, PUT? If
its there then how we can configure it? Is there any consequences of
increasing the same.





--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Thread-pool-for-partition-aware-operations-tp10393.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Thread pool for partition aware operations

[vkulichenko <va...@gmail.com>]

Anything executed on IgniteCompute API is executed in public pool (size is
configured via IgniteConfiguration.publicThreadPoolSize property), while all
cache operations including entry processor are executed in system pool
(IgniteConfiguration.publicSystemPoolSize property). Sizes for both pools
are twice number of cores by default, which is a enough for majority of
cases. Whether it's good to change or not, depends on your application.

-Val



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Thread-pool-for-partition-aware-operations-tp10393p10405.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.