qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPIDJMS-404) Performance regressions on some platforms using new ProviderFuture implementation
Date Wed, 18 Jul 2018 16:42:00 GMT

    [ https://issues.apache.org/jira/browse/QPIDJMS-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16548062#comment-16548062

ASF subversion and git services commented on QPIDJMS-404:

Commit 264a9a9b6c5d8d8c11a995b7b02289b2938d77ba in qpid-jms's branch refs/heads/master from
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=264a9a9 ]

QPIDJMS-404 Add variants of ProviderFuture for perf tuning

Adds three variations on ProviderFuture that allow for tuning on
platforms that don't benefit from the spin / wait pattern used in
the current implementation and default to using a variant that does
not park on windows to avoid unpredictably long parks that result
in performance decreases due to missing the event completion.

> Performance regressions on some platforms using new ProviderFuture implementation
> ---------------------------------------------------------------------------------
>                 Key: QPIDJMS-404
>                 URL: https://issues.apache.org/jira/browse/QPIDJMS-404
>             Project: Qpid JMS
>          Issue Type: Bug
>          Components: qpid-jms-client
>    Affects Versions: 0.34.0
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>            Priority: Major
>             Fix For: 0.35.0
> The new ProviderFuture implementation introduced in 0.34.0 relies on a stepped spin /
wait algorithm that backs off the spin using yeilds and short parks which will eventually
end in a wait / notify pattern if the event hasn't completed.  On some platforms the length
of a park can be substantially longer than requested which leads to missing the event completion
for long periods of time reducing performance. 
> Introduce a set of ProviderFuture implementations that can be used on platforms where
the stepped spin / wait variant causes regressions in performance. 

This message was sent by Atlassian JIRA

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

View raw message