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

Alex Rudyy commented on QPID-4089:
----------------------------------

Hi Keith,

I fixed the compilation issue in an updated patch.
                
> Add latency tests into Java Performance Tests
> ---------------------------------------------
>
>                 Key: QPID-4089
>                 URL: https://issues.apache.org/jira/browse/QPID-4089
>             Project: Qpid
>          Issue Type: Task
>          Components: Java Performance Tests
>    Affects Versions: 0.17
>            Reporter: Alex Rudyy
>            Assignee: Keith Wall
>             Fix For: 0.17
>
>         Attachments: 
> 0001-QPID-4089-Add-latency-tests-into-java-performance-te.patch
>
>
> We need to implement a group of tests measuring latency metrics (minimum 
> latency, maximum latency, average latency, standard deviation) by varying the 
> following attributes:
> queue type
> message size
> number of producers and consumers
> selectors
> The publishing rate should be deliberately limited in such tests to never 
> throttle the broker or exceed the consumption rate.
> Ideally, a special configuration parameter like expectedPublishingRate can be 
> added to control publishing, however, we can use currently implemented 
> "interval" parameter. We can also publish data in small batches with delays 
> between batches.
> Also, it would be interesting to see comparison of latency vs throughput by 
> varying the publishing rate.
> Publishing in AA mode is only required for initial latency tests.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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

Reply via email to