incubator-s4-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Flavio Junqueira (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (S4-62) Multithreaded Streams
Date Fri, 22 Jun 2012 08:23:43 GMT

    [ https://issues.apache.org/jira/browse/S4-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399206#comment-13399206
] 

Flavio Junqueira commented on S4-62:
------------------------------------

When you say that a PE blocks upon an event, are you referring to waiting on an I/O or something
similar, or simply being CPU intensive. In general, I would think that network is the primary
bottleneck, but I'm not really sure what it is for S4. Has anyone verified it? 

Having PEs that block upon an event does not sound like a good idea, but it would be interesting
to see a use case if you or anyone else is aware of any.
                
> 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

       

Mime
View raw message