[jira] [Updated] (IGNITE-21494) Data Streamer: use one shared executor per node for flushTimer

2024-04-05 Thread Pavel Tupitsyn (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-21494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn updated IGNITE-21494:

Description: 
Currently, every *StreamerSubscriber* instance creates a new 
*SingleThreadScheduledExecutor* for the *flushTimer*, which means a new thread 
for every streamer.

This is excessive. One executor per node or client should be enough.

  was:
Currently, every *StreamSubscriber* instance creates a new 
*SingleThreadScheduledExecutor* for the *flushTimer*, which means a new thread 
for every streamer.

This is excessive. One executor per node or client should be enough.


> Data Streamer: use one shared executor per node for flushTimer
> --
>
> Key: IGNITE-21494
> URL: https://issues.apache.org/jira/browse/IGNITE-21494
> Project: Ignite
>  Issue Type: Improvement
>  Components: thin client
>Affects Versions: 3.0.0-beta1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> Currently, every *StreamerSubscriber* instance creates a new 
> *SingleThreadScheduledExecutor* for the *flushTimer*, which means a new 
> thread for every streamer.
> This is excessive. One executor per node or client should be enough.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (IGNITE-21494) Data Streamer: use one shared executor per node for flushTimer

2024-02-08 Thread Pavel Tupitsyn (Jira)


 [ 
https://issues.apache.org/jira/browse/IGNITE-21494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn updated IGNITE-21494:

Description: 
Currently, every *StreamSubscriber* instance creates a new 
*SingleThreadScheduledExecutor* for the *flushTimer*, which means a new thread 
for every streamer.

This is excessive. One executor per node or client should be enough.

> Data Streamer: use one shared executor per node for flushTimer
> --
>
> Key: IGNITE-21494
> URL: https://issues.apache.org/jira/browse/IGNITE-21494
> Project: Ignite
>  Issue Type: Improvement
>  Components: thin client
>Affects Versions: 3.0.0-beta1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> Currently, every *StreamSubscriber* instance creates a new 
> *SingleThreadScheduledExecutor* for the *flushTimer*, which means a new 
> thread for every streamer.
> This is excessive. One executor per node or client should be enough.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)