Implemented. Will appear in master soon. Benchmarks shown no performance
drop.
On Thu, Sep 29, 2016 at 3:16 PM, Vladimir Ozerov
wrote:
> Ignite node thread dump after applying quick and dirty solution - just
> added *ThreadPoolExecutor.allowCoreThreadTimeOut(true)* to base
Ignite node thread dump after applying quick and dirty solution - just
added *ThreadPoolExecutor.allowCoreThreadTimeOut(true)* to base thread pool:
"srvc-deploy-#20%null%"
"exchange-worker-#19%null%"
"ttl-cleanup-worker-#18%null%"
"grid-time-coordinator-#17%null%"
Created ticket: https://issues.apache.org/jira/browse/IGNITE-4001
On Thu, Sep 29, 2016 at 12:25 PM, Alexey Kuznetsov
wrote:
> Just as idea -
>
> if we implement stop thread after some idle time, may be it make sense to
> add a line to log about this?
>
> --
> Alexey
Just as idea -
if we implement stop thread after some idle time, may be it make sense to
add a line to log about this?
--
Alexey Kuznetsov
+100500
We need to stop threads after some idle time.
Sergi
2016-09-29 11:26 GMT+03:00 Vladimir Ozerov :
> Igniters,
>
> If you look at a thread dump of an idle Ignite instance, you will find
> billions threads there. System pool, public pool, management pool, IGFS
>
Igniters,
If you look at a thread dump of an idle Ignite instance, you will find
billions threads there. System pool, public pool, management pool, IGFS
pool, data streamer pool, etc..
I think we can easily do the following with no risk to performance:
1) Set core size to zero to all thread