[jira] [Updated] (S4-62) Multithreaded Streams

2012-08-23 Thread Matthieu Morel (JIRA)

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

Matthieu Morel updated S4-62:
-

Fix Version/s: 0.6

> Multithreaded Streams
> -
>
> Key: S4-62
> URL: https://issues.apache.org/jira/browse/S4-62
> Project: Apache S4
>  Issue Type: Improvement
>Affects Versions: 0.5.0
>Reporter: Daniel Gómez Ferro
> Fix For: 0.6
>
> Attachments: S4-62-multithreaded-streams.patch, 
> S4-62-multithreaded-streams.patch
>
>
> Currently, each Stream has one Thread in charge of processing the incoming 
> events on the appropriate PE. If one PE blocks it's execution while 
> processing an event, the whole Stream would be blocked. The current solution 
> is for a PE to manage his own async thread, which I don't think it's nice.
> It would be better to have a configurable number of threads that would take 
> care of the execution of the incoming events.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (S4-62) Multithreaded Streams

2012-06-22 Thread Matthieu Morel (JIRA)

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

Matthieu Morel updated S4-62:
-

Affects Version/s: 0.5

> Multithreaded Streams
> -
>
> Key: S4-62
> URL: https://issues.apache.org/jira/browse/S4-62
> Project: Apache S4
>  Issue Type: Improvement
>Affects Versions: 0.5
>Reporter: Daniel Gómez Ferro
> Attachments: S4-62-multithreaded-streams.patch, 
> S4-62-multithreaded-streams.patch
>
>
> Currently, each Stream has one Thread in charge of processing the incoming 
> events on the appropriate PE. If one PE blocks it's execution while 
> processing an event, the whole Stream would be blocked. The current solution 
> is for a PE to manage his own async thread, which I don't think it's nice.
> It would be better to have a configurable number of threads that would take 
> care of the execution of the incoming events.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (S4-62) Multithreaded Streams

2012-06-22 Thread JIRA

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

Daniel Gómez Ferro updated S4-62:
-

Attachment: S4-62-multithreaded-streams.patch

I'm updating the tests to reuse the classes introduced in S4-63, which is more 
likely to get integrated soon.

> Multithreaded Streams
> -
>
> Key: S4-62
> URL: https://issues.apache.org/jira/browse/S4-62
> Project: Apache S4
>  Issue Type: Improvement
>Reporter: Daniel Gómez Ferro
> Attachments: S4-62-multithreaded-streams.patch, 
> S4-62-multithreaded-streams.patch
>
>
> Currently, each Stream has one Thread in charge of processing the incoming 
> events on the appropriate PE. If one PE blocks it's execution while 
> processing an event, the whole Stream would be blocked. The current solution 
> is for a PE to manage his own async thread, which I don't think it's nice.
> It would be better to have a configurable number of threads that would take 
> care of the execution of the incoming events.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (S4-62) Multithreaded Streams

2012-06-22 Thread JIRA

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

Daniel Gómez Ferro updated S4-62:
-

Attachment: S4-62-multithreaded-streams.patch

This patch introduces an ExecutorService per Stream with a configurable maximum 
number of threads (default is 1).

A few tests are included.

> Multithreaded Streams
> -
>
> Key: S4-62
> URL: https://issues.apache.org/jira/browse/S4-62
> Project: Apache S4
>  Issue Type: Improvement
>Reporter: Daniel Gómez Ferro
> Attachments: S4-62-multithreaded-streams.patch
>
>
> Currently, each Stream has one Thread in charge of processing the incoming 
> events on the appropriate PE. If one PE blocks it's execution while 
> processing an event, the whole Stream would be blocked. The current solution 
> is for a PE to manage his own async thread, which I don't think it's nice.
> It would be better to have a configurable number of threads that would take 
> care of the execution of the incoming events.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira