DataPower

 View Only
  • 1.  Inbound and Outbound Req Calculation

    Posted Thu December 02, 2021 09:38 AM
    Is there any formula/algorithm or anything to count or calculate datapower requests with hardware specification on the basis of api calls, payload size to work seamlessly.

    ------------------------------
    Anurag Gupta
    ------------------------------


  • 2.  RE: Inbound and Outbound Req Calculation

    Posted Fri December 03, 2021 09:59 AM
    Hi Anurag, I hope you are doing well!

    I am answering this with the assumption you want to size a deployment for a future use case. Let me know if that is not the case.

    Your IBM account team has access to an internal sizing tool that can help you with that. You would need to provide them with scenario type, payload  sizes, desired transaction per second rate, and head room you wish to have at peak.

    If you are not sure who your IBM account team are, let me know and I will put you in touch with them.

    Hope it helps!

    Thanks!

    ------------------------------
    Bruno R Neves
    Integration Specialist
    IBM
    Tampa FL
    ------------------------------



  • 3.  RE: Inbound and Outbound Req Calculation

    Posted Tue December 07, 2021 01:06 AM
    Hi Bruno,

    Thanks for you response.
     
    As per requirement I am assuming 5 lac. approx. API transaction per day, with an average payload size. What should be basic infrastructure required for such specifications in Datapower.

    Regards



    ------------------------------
    Anurag Gupta
    ------------------------------



  • 4.  RE: Inbound and Outbound Req Calculation

    Posted Tue December 07, 2021 01:08 AM
    Can you also provide any reference to internal sizing tool if it is accessible.

    ------------------------------
    Anurag Gupta
    ------------------------------



  • 5.  RE: Inbound and Outbound Req Calculation
    Best Answer

    Posted Tue December 07, 2021 05:18 PM

    Hi Anurag, I hope you are well!

    It sounds like your system is expecting to see 500,000 API calls a day. Dividing this number by 8 business hours, we are talking 62,500 API calls per hour. Further dividing by 60 minutes and then by 60 seconds, we are looking at ~18 API calls per second (TPS).

    The API Gateway component (DataPower) is the component that will see the main impact of these API calls, as during runtime it will be enforcing security, performing payload validation, perhaps some message transformation, etc

    In this presentation (refer to slide 10), you can see that we tested both a virtual and a physical appliance against 3 use cases, and we observed the following (for 4KB payload and CPU at 100% utilization):

    1. Complex testing (map+invoke+map)
    Virtual 8 vCPU = 912 TPS
    Physical IDG X2 = 5,088 TPS
    2. Medium testing (OAuth+invoke)
    Virtual 8 vCPU = 4,271 TPS
    Physical IDG X2 = 25,571 TPS
    3. Simple testing (invoke)
    Virtual 8 vCPU = 5,144 TPS
    Physical IDG X2 = 29,932 TPS

    The numbers above will be different if you change the complexity of the API or the request and response sizes, but it should give you an idea.

    From the information you have provided so far, it sounds like that the minimum requirement for DataPower (4 vCPU) would provide sufficient processing power to run your use case. We however recommend you to test in your own environment with your own equipment, as other factors, such as network, hypervisor engine, processor and server models, etc, may affect these results.

    Does this help?

    ------------------------------
    Bruno R Neves
    Integration Specialist
    IBM
    Tampa FL
    ------------------------------



  • 6.  RE: Inbound and Outbound Req Calculation

    Posted Wed December 08, 2021 04:58 AM
    Hi Bruno,

    Thanks a lot for your assistance.
    I was looking for exactly information which you provided to me.

    In similar way, Is the information available of other resources like RAM and Storage for Virtual Environment? 

    Regards

    ------------------------------
    Anurag Gupta
    ------------------------------



  • 7.  RE: Inbound and Outbound Req Calculation

    Posted Wed December 08, 2021 11:30 AM
    Hi Anurag, glad to assist!

    As for RAM consumption on the API Gateway, it will be highly dependent on the peak TPS and the API logic. Say for example you have a peak of 30 TPS and the combined request/response payload is 1 MB. As part of your API design you perform at least one parse and one transform action. Every time you parse or transform a payload, a copy of the payload may be created in memory. So if your combined payloads is 1 MB you could consume 3 MB now. If you see 30 calls of that same API in a given second, that is 30 times 3 MB, or 90 MB. Minimum requirement for the API Gateway is at least 8 GB, so you would be more than okay in this case. However, as the TPS or API numbers grow, you would want to revisit your decisions. You can also keep track of resource consumption as your environment grows and use the data to plan for future changes.

    In terms of storage, the API Gateway component by definition is a stateless runtime, meaning it won't need to store anything to do its job, other than configuration, message schemas, and perhaps code.

    Let me know if your solution goes beyond just the DataPower component. If you are planning to use API Connect for example, you may have to better plan for storage primarily on the Dev Portal and Analytics components.

    ------------------------------
    Bruno R Neves
    Integration Specialist
    IBM
    Tampa FL
    ------------------------------