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

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

                Author: ASF GitHub Bot
            Created on: 15/Nov/20 17:39
            Start Date: 15/Nov/20 17:39
    Worklog Time Spent: 10m 
      Work Description: michaelandrepearce edited a comment on pull request 
#3343:
URL: https://github.com/apache/activemq-artemis/pull/3343#issuecomment-727607065


   Could actually just make the extra composite address entry at time of queue 
creation and remove at queue deletion into the queue binding lookup map, then 
you don't need to worry if you get composite or not its going to be a simple 
lookup to get the queue binding in the same maps. And no need for indexof or 
anything. And like wise no need to have a cache either risking cache misses, as 
would be maintained by add remove queue.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


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

    Worklog Id:     (was: 511996)
    Time Spent: 3h  (was: 2h 50m)

> Provide JMH Benchmarks for Artemis
> ----------------------------------
>
>                 Key: ARTEMIS-2996
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2996
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Tests
>            Reporter: Francesco Nigro
>            Assignee: Francesco Nigro
>            Priority: Major
>          Time Spent: 3h
>  Remaining Estimate: 0h
>
> In order to reliably measure performance of many Artemis component would be 
> welcome to implement some https://github.com/openjdk/jmh benchmarks to be 
> used for development purposes ie not part of the release



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to