Make rate limiting decision based only on ingress request headers

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The idea: do as little work as possible, and use as little information as possible, in order to make a rate limiting decision. In the common case this means we only need an ingress OP_MSG requestId and moreToCome in order to produce a correct response (excluding OP_COMPRESSED cases for now). Once we have those bytes, we can "drain" the rest of the response buffer without copies or allocations, showing a 14% performance improvement on the workload introduced in DEVPROD-33860

            Assignee:
            Matt Broadstone
            Reporter:
            Matt Broadstone
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: