Uploaded image for project: 'Qpid Proton'
  1. Qpid Proton
  2. PROTON-2591

[protonj2] Use an appropriate initial allocation size for the client message encoder

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • protonj2-1.0.0-M7
    • protonj2-1.0.0-M8
    • protonj2
    • None

    Description

      The message encoder in the client is using a default allocation API for the output buffer which results in a buffer that is almost always to small for the encoded message leading to at least one resize and copy of the bytes as they are encoded.  The client should choose a more realistic size for the initial allocation that at least allows a small message to be encoded into the output buffer without a resize.

      Attachments

        Activity

          People

            tabish Timothy A. Bish
            tabish Timothy A. Bish
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: