Huge performance degradation in qpid-java-0.14-3 when using independent Spout + Drain messaging pattern

Solution In Progress - Updated -

Issue

When comparing throughput of qpid-java clients (0.10-11 and 0.18-2 versions), the most simple message pattern "run one Spout and one Drain independently" shows huge performance degradation in message throughput: around 40-50% drop.

tcp_nodelay explicitly set in every test (both to be enabled and disabled) to get rid of the impact of BZs 761186 / 753238.

The ratio of throughput degradation is very similar regardless if tests run against a standalone broker or 3node cluster. Also broker version has no impact to the ratio.

Environment

  • Red Hat MRG 2.2
  • qpid-java-*-0.18-2

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content