Layer7 API Management

  • 1.  Limit Message Size Assertion Latency

    Posted Aug 18, 2017 01:13 PM

    Usage of the "Limit Message Size" assertion in a policy to allow request payloads larger than the default limit to flow through is introducing significant latency. Any particular reason towards the same ? Any recommended best practices towards its usage ?



  • 2.  Re: Limit Message Size Assertion Latency

    Posted Aug 21, 2017 04:21 AM

    Hi,

    There are various cluster wide property to limit message size in the policy. however there are some server level configuration as well for large message which can be used for optimizing performance for response. for more details refer below base article present in the CA website.

     

    API gateway: Optimizing for Large Files and Messages 

     

    Hope this will help.

     

    Thanks,

    Grajesh



  • 3.  Re: Limit Message Size Assertion Latency

    Posted Aug 21, 2017 04:28 AM

    I am aware of the multiple options. However my use case is to apply the same at an individual API level. The payload sizes are in the range of 2 MB - 15 MB. 



  • 4.  Re: Limit Message Size Assertion Latency
    Best Answer

    Broadcom Employee
    Posted Nov 15, 2017 12:57 PM

    Arvind,

     

    The usage of the limit size assertion should not introduce any latency as it only views the content size header and evaluates the size of the payload. What could be impacting the flow is where you are streaming or not streaming in the request or back the response. For inbound there is an assertion Configure message streaming (only for inbound requests) and as long as the payload is not modified then it will stream through or for responses if you include anything after the HTTP Routing assertion that inspects or changes the payload then it will not stream back.

     

    Sincerely,

     

    Stephen Hughes

    Director, CA Support