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

ASF subversion and git services commented on QPIDJMS-418:
---------------------------------------------------------

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

QPIDJMS-418 Optimize usage of Symbol types to reduce overhead

The code is currently doing many Symbol.valueOf calls for each message
on send and receive where it should be using cached Symbol values to
avoid the overhead of the Symbol objects cache lookups and string
compares.  Clean up some other ares where we process Symbols to reduce
overhead on send and receive.


> Clean up the usage of Symbol type and conversion to Symbol from String
> ----------------------------------------------------------------------
>
>                 Key: QPIDJMS-418
>                 URL: https://issues.apache.org/jira/browse/QPIDJMS-418
>             Project: Qpid JMS
>          Issue Type: Improvement
>          Components: qpid-jms-client
>    Affects Versions: 0.37.0
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>            Priority: Major
>             Fix For: 0.38.0
>
>
> The code currently does a lot more work than needed on each send converting 
> from String values into Symbol types to fill in the proton-j message 
> structure prior to encoding. We can now keep all our commonly used values in 
> static proton-j Symbol instances and request the cached String view that each 
> now maintains when we need a String representation. The current proton-j API 
> make this need for String less relevant that it once was so our overhead on 
> send can be significantly reduced with minimal changes.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to