You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Jens Reimann (JIRA)" <ji...@apache.org> on 2018/08/07 15:22:00 UTC
[jira] [Created] (PROTON-1911) Performance issue in
EncoderImpl#writeRaw(String)
Jens Reimann created PROTON-1911:
------------------------------------
Summary: Performance issue in EncoderImpl#writeRaw(String)
Key: PROTON-1911
URL: https://issues.apache.org/jira/browse/PROTON-1911
Project: Qpid Proton
Issue Type: Improvement
Components: proton-j
Affects Versions: proton-j-0.28.0, proton-j-0.22.0
Reporter: Jens Reimann
Attachments: qpid_encode_1.png, qpid_encode_2.png, qpid_encode_3.png, qpid_encode_4.png
While digging into performance issues in the Eclipse Hono project I noticed a high consumption of CPU time when encoding AMQP messages using proton-j.
I made a small reproducer and threw the same profiler at it, here are the results:
As you can see in the attach screenshot (the first is the initial run with the current code) most of the time is consumed in EncoderImpl#writeRaw(String). This due to the fact that is call "put" for every byte it want to encode.
The following screenshots are from a patched version which uses a small thread local buffer to locally encode the raw data and then flush it to the buffer in bigger chunks.
Screenshot 3 and 4 show the improve performance, but also show that the memory consumption stays low.
--
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