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

Rajith Attapattu commented on QPID-3941:
----------------------------------------

Weston, thanks for the pointer. However I had already done the work and have 
just committed most of it.
The core logic was mostly there and I had to just move the code around and 
add/modify as needed.

What's remaining to be done is,
1. modify existing scripts
2. add wrapper scripts for qpid-send and qpid-receive to have identical options 
as the c++ version
3. update comments in the code
4. add some documentation describing the existing tools and how to use QpidSend 
and QpidReceieve as building blocks in scripts to create different types of 
testing tools.

With the qpid-send and qpid-receive wrapper scripts, the jms version can be 
used with the qpid-cpp-benchmark tool without any modification.
What we could do is to rename the qpid-cpp-benchmark tool as qpid-benchmark, 
move it under a top level dir, and allow the paths to be configured so it can 
be easily used with the c++ or jms version or mix and match them.
                
> Add the jms version of QpidSend and QpidReceive
> -----------------------------------------------
>
>                 Key: QPID-3941
>                 URL: https://issues.apache.org/jira/browse/QPID-3941
>             Project: Qpid
>          Issue Type: New Feature
>          Components: Java Client
>            Reporter: Rajith Attapattu
>            Assignee: Rajith Attapattu
>             Fix For: 0.17
>
>
> If we could come with near identical versions of the c++ QpidSend and 
> QpidReceive we could do meaningful comparisons between the c++ and JMS 
> clients.
> This can be very helpful when figuring out if a problem is on broker or 
> client side. Ex if both the c++ and jms versions exibhit a similar 
> behavior/trend/pattern we could make a reasonable conclusion that the issue 
> might be on the broker side.
> This could also be very helpful in identifying weak points in a particular 
> client if there is a huge difference in behavior for a given use case.
> The goal is to ensure that we use identical options and behavior to ensure 
> they are as close as possible.
> This will allow us to turn qpid-cpp-benchmark into a generic benchmark tool, 
> where we can use it for both clients or mix and match (ex JMS receiver with 
> C++ sender).

--
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