You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2018/07/13 10:55:00 UTC

[jira] [Commented] (QPIDJMS-402) Massive performance degradation in 0.34.0

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

Robbie Gemmell commented on QPIDJMS-402:
----------------------------------------

It would be more helpful if you gave a fully runnable reproducer (whether. a patch into the build or an entirely separate thing) and not just some code in isolation. That way know we are definitely doing the same thing in the same way, and folks can spend time looking into the issue rather than time figuring out what to do to get it running.

I didn't see the same when I eventually ran your reproducer. 0.34.0 was significantly faster than 0.33.0 in my runs. On my ageing laptop I saw around 3000/s for 0.33.0, whereas for 0.34.0 I saw around 5000/s. Both our numbers seemed surprisingly low, so I then had a closer look at the reproducer code.

A new MessageProducer is created and closed for every message sent, capping performance from the outset since that adds two synchronous operations per message. The async send inbetween them avoids adding another, though. The Semaphore stuff seems essentially dead code given how it is[n't] used, though it wouldn't normally have any effect if it were in play given the send process is still governed by message credit which is rarely going to allow that large a window to actually form.

Changing the reproducer to re-use its sender, I got around 48,000/s with 0.33.0 and then around 71,000/s with 0.34.0 on my laptop.

Robbie

> Massive performance degradation in 0.34.0
> -----------------------------------------
>
>                 Key: QPIDJMS-402
>                 URL: https://issues.apache.org/jira/browse/QPIDJMS-402
>             Project: Qpid JMS
>          Issue Type: Bug
>          Components: qpid-jms-client
>    Affects Versions: 0.34.0
>         Environment: Windows 7x64 + Oracle JDK 8u161x64
> Windows 7x64 + Open JDK 8u171x64
> CloudFoundry (Ubuntu Trusty) + Open JDK 8u172x64
>            Reporter: Johan Stenberg
>            Priority: Critical
>         Attachments: QpidJms402_PerfTest.java
>
>
> This is a followup issue for [http://qpid.2158936.n2.nabble.com/qpid-jms-Severe-performance-issue-after-upgrading-from-0-33-0-to-0-34-0-td7678052.html]
> I am attaching a simple test case that shows the issue. When I use qpid jms 0.33 I get 2000msg/s send + receive on my local machine. When I switch to 0.34 the message rate drops to 20msg/s.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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