incubator-awf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tony Stevenson (Moved) (JIRA)" <>
Subject [jira] [Moved] (AWF-36) Multithreaded Deft to have multiple load-balanced IOLoop instance
Date Wed, 29 Feb 2012 10:10:00 GMT


Tony Stevenson moved DEFT-139 to AWF-36:

    Reporter: Niklas Gustavsson
         Key: AWF-36  (was: DEFT-139)
     Project: Apache AWF  (was: Deft)
> Multithreaded Deft to have multiple load-balanced IOLoop instance
> -----------------------------------------------------------------
>                 Key: AWF-36
>                 URL:
>             Project: Apache AWF
>          Issue Type: Bug
>            Reporter: Niklas Gustavsson
> The main idea behind is to be able to have more than one IOLoop thread running in the
JVM, so Defft can use every single core or CPU of the hosting system. I did something like
that in my forked project.
> I see two orientation for this: 
> - One infinite loop using a selector to listen for incoming request (accept) and pushing
accepted sockets to one or more infinite thread loop. This is what I did in my fork :). The
infinite thread loop use another selector to handle read, write and all other operations,
so channel events are still executed in the same single thread.
> - One selector holding listening sockets is shared between multiple infinite IOLoop threads.
Each IOLoop hold its own selector for read and write operations. There should be a lock on
the shared selector but this may be easier to develop.
> My purpose is to allow Deft to execute on all available CPU cores without breaking the
infinite loop philosophy.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message