[jira] [Commented] (PROTON-2130) Improve epoll_wait processing in epoll proactor

["ASF subversion and git services (Jira)" <ji...@apache.org>]

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

ASF subversion and git services commented on PROTON-2130:
---------------------------------------------------------

Commit b3d1004800b569f69ebea58366021f7ddcd64692 in qpid-proton's branch refs/heads/master from Cliff Jansen
[ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=b3d1004 ]

PROTON-2130: epoll proactor: fix unwritten output bytes, pick up PROTON-2030 and PROTON-2131


> Improve epoll_wait processing in epoll proactor
> -----------------------------------------------
>
>                 Key: PROTON-2130
>                 URL: https://issues.apache.org/jira/browse/PROTON-2130
>             Project: Qpid Proton
>          Issue Type: Improvement
>          Components: proton-c
>    Affects Versions: proton-c-0.29.0
>            Reporter: Clifford Jansen
>            Assignee: Clifford Jansen
>            Priority: Major
>
> Change epoll proactor to use epoll_wait() more efficiently and more canonically.
> Old way: each thread without work called epoll_wait() for 1 event.
> New: when known work exhausted, only one thread calls epoll_wait for N events and schedules work for the other threads to execute.
> The downside to the old way is that for each event, all threads in epoll_wait() are woken up but only one "wins" (obtaining the event to process) while the rest go back to sleep.
> In addition to wasteful use of cpu, this behavior also shows up in performance monitoring tools and clutters the analysis of profiling data and flame graphs.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org