Qpid
  1. Qpid
  2. QPID-4116

Allow qpid-cpp-benchmark to run qpid-send and qpid-receive from specified directories

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 0.16
    • Fix Version/s: 0.21
    • Component/s: C++ Client
    • Labels:
      None

      Description

      I am proposing a trivial patch allowing to specify directories where to run qpid-send and/or qpid-receive from. This would allow using qpid-cpp-benchmark against various instances of qpid-send and/or qpid-receive (i.e. written in various clients to allow simple performance comparison of the clients - see QPID-4115).

      Two options are added - one to specify path to qpid-send, and second to specify path to qpid-receive. This would allow e.g. testing scearios with C++ producers and Java consumers.

      Default behavior remains the same, so the patch is backward compatible.

      Also due to QPID-4115, I would suggest re-naming qpid-cpp-benchmark to qpid-benchmark, as it will not be tied just to qpid-[send|receive] written in C++.

        Activity

        Hide
        Pavel Moravec added a comment -

        Patch allowing to specify path to qpid-send and/or qpid-receive.

        Show
        Pavel Moravec added a comment - Patch allowing to specify path to qpid-send and/or qpid-receive.
        Hide
        Gordon Sim added a comment -

        Patch for new path options commited as http://svn.apache.org/viewvc?view=revision&revision=r1446578. Thanks Pavel!

        I've left the name as it is for now pending some more thought on how to transition smoothly.

        Show
        Gordon Sim added a comment - Patch for new path options commited as http://svn.apache.org/viewvc?view=revision&revision=r1446578 . Thanks Pavel! I've left the name as it is for now pending some more thought on how to transition smoothly.

          People

          • Assignee:
            Gordon Sim
            Reporter:
            Pavel Moravec
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development