[ 
https://issues.apache.org/jira/browse/ARTEMIS-2170?focusedWorklogId=189326&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-189326
 ]

ASF GitHub Bot logged work on ARTEMIS-2170:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 24/Jan/19 06:38
            Start Date: 24/Jan/19 06:38
    Worklog Time Spent: 10m 
      Work Description: franz1981 commented on issue #2427: ARTEMIS-2170 
Optimized CoreMessage's checkProperties and cleanupInternalProperties methods
URL: https://github.com/apache/activemq-artemis/pull/2427#issuecomment-457084424
 
 
   @michaelandrepearce yep, it seems ok from the CI pov: there are just a 
couple of failures that seems unrelated to this PR :+1
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 189326)
    Time Spent: 6h 50m  (was: 6h 40m)

> Optimized CoreMessage's checkProperties and cleanupInternalProperties methods
> -----------------------------------------------------------------------------
>
>                 Key: ARTEMIS-2170
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2170
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: Broker
>            Reporter: Francesco Nigro
>            Assignee: Francesco Nigro
>            Priority: Minor
>          Time Spent: 6h 50m
>  Remaining Estimate: 0h
>
> CoreMessage::checkProperties perform too many volatile read/write and has a 
> too big body just to handle exceptional cases, while 
> cleanupInternalProperties is called on the hot path of session send, but is 
> performing too many synchronized operations and loopup on TypedProperties.



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

Reply via email to