Uploaded image for project: 'Qpid'
  1. Qpid
  2. QPID-5910

Throughput regression relative to 0.14

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.22
    • Fix Version/s: 0.29
    • Component/s: None
    • Labels:
      None

      Description

      If you use qpid-latency-test, hold message size constant, and gradually increase the sending rate (in several tests) you will sooner or later reach a point at which the messaging system's ability to handle throughput saturates. When that happens, latency will go sky-high. (I have producer flow-control turned off to be able to compare vs. older code.)

      The latest code reaches throughput saturation significantly earlier than older code. (i.e. at a lower sending rate.)

      Also, using 'perf' to help analyze the code, recent code is executing significantly fewer instructions per second than older code.

      This probably indicates that come parts of the code are spending too much time while a lock is held – thus preventing other threads from fulfilling their destiny, and having an effect on overall throughput.

        Attachments

          Activity

            People

            • Assignee:
              mgoulish Michael Goulish
              Reporter:
              mgoulish Michael Goulish
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: