You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@ignite.apache.org by VeenaMithare <v....@cmcmarkets.com> on 2020/10/03 13:11:49 UTC

Re: Ignite thread pool configuration

I noticed that the DataStreamer thread pool size seems to be around 32 in my
local machine. In our cluster setup we dont stream data from any external db
. We use native persistence. Do you think it makes sense to reduce this pool
size for both server and client configuraiton. I am not sure if this pool
will ever be used in our project.





--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite thread pool configuration

Posted by VeenaMithare <v....@cmcmarkets.com>.

Thanks Denis,

regards,
Veena.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite thread pool configuration

Posted by Denis Magda <dm...@apache.org>.

Give it a try but do some load testing close to your production workload.
And then ramp the numbers up if needed.

-
Denis


On Mon, Oct 5, 2020 at 12:56 AM VeenaMithare <v....@cmcmarkets.com>
wrote:

> Thanks Denis,
>
> I am thinking of setting the below thread pools as this on both client and
> server since we dont use data streamer, IGFS or Peer Class loading:
>
>         <property name="dataStreamerThreadPoolSize" value="4"/>
>         <property name="igfsThreadPoolSize" value="4"/>
>         <property name="peerClassLoadingThreadPoolSize" value="4"/>
>
> Also our thick clients dont connect using REST . So thinking of adding the
> below configuration on our thick client configuration.
>
>         <property name="connectorConfiguration">
>             <bean
> class="org.apache.ignite.configuration.ConnectorConfiguration">
>                 <property name="threadPoolSize" value="4"/>
>             </bean>
>         </property>
>
> Hope that is okay ?
>
> regards,
> Veena.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Ignite thread pool configuration

Posted by VeenaMithare <v....@cmcmarkets.com>.

Thanks Denis,

I am thinking of setting the below thread pools as this on both client and
server since we dont use data streamer, IGFS or Peer Class loading: 

        <property name="dataStreamerThreadPoolSize" value="4"/>
        <property name="igfsThreadPoolSize" value="4"/>
        <property name="peerClassLoadingThreadPoolSize" value="4"/>

Also our thick clients dont connect using REST . So thinking of adding the
below configuration on our thick client configuration.

        <property name="connectorConfiguration">
            <bean
class="org.apache.ignite.configuration.ConnectorConfiguration">
                <property name="threadPoolSize" value="4"/>
            </bean>
        </property>

Hope that is okay ?

regards,
Veena.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite thread pool configuration

Posted by Denis Magda <dm...@apache.org>.

You can certainly reduce its size (
https://ignite.apache.org/docs/latest/perf-and-troubleshooting/thread-pools-tuning#data-streamer-pool).
But at the same time created but unused threads are just some objects that
consume a bit of memory but don't use any CPU resources (until you start
using those).

-
Denis

On Sat, Oct 3, 2020 at 6:12 AM VeenaMithare <v....@cmcmarkets.com>
wrote:

> I noticed that the DataStreamer thread pool size seems to be around 32 in
> my
> local machine. In our cluster setup we dont stream data from any external
> db
> . We use native persistence. Do you think it makes sense to reduce this
> pool
> size for both server and client configuraiton. I am not sure if this pool
> will ever be used in our project.
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>