ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vdpyatkov <vldpyat...@gmail.com>
Subject Re: Distributed Closures VS Executor Service
Date Fri, 17 Mar 2017 15:47:45 GMT
Hi,

Ignite compute[2] is the general mechanism to execute distributed task. If
you are mean Executor Service[1], it is only convenient API.
Distributed tasks will be stay at queue if public thread pool is full.
If you need to increase thread count in public pull you can do that[3].
<bean class="org.apache.ignite.configuration.IgniteConfiguration">
    ... 
    <property name="publicThreadPoolSize" value="64"/>

[1]: https://apacheignite.readme.io/docs/executor-service
[2]: https://apacheignite.readme.io/docs/distributed-closures
[3]:
https://apacheignite.readme.io/docs/performance-tips#section-configure-thread-pools



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Distributed-Closures-VS-Executor-Service-tp11192p11287.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Mime
View raw message