IBM Support

How do I size my API Connect environment?

Question & Answer


Question

How do I size my API Connect environment?

Answer

On Demand Consulting
Author: Uday Pilai


Overview

This articles provides tips for sizing your API Connect environment.

Intended Audience

Administrators planning to build a new API Connect environment.

Key components in an API Connect Architecture

  • DataPower Gateway (Physical or Virtual)
  • Management Server (Virtual)
  • Advanced Portal (Virtual)

Sizing tips for DataPower Gateways

  1. Sizing API Connect is different than sizing for DataPower even though Datapower is the primary transaction gateway for all traffic going through the system
  2. IDG 9006 Physical Appliances paired along with a single management node @ 4cpu & 16 gb of RAM will push through roughly 3000tp
  3. The speed of the processors on the host system have a significant impact on the throughput of the virtual Gateways.
                  Test ran on 2 different stacks each using 2 GWs with 8vCPUs and 8GB of memory.
                  The first stack used Intel Xeon E5-2680 processors running at 2.7 GHz and achieved a throughput of around 2390 tps.
                  The second stack used Intel Xeon E7-8860 processors running at 2.26 GHz and achieved a throughput of around 1990 tps. You can see this represents a 25% reduction which is very significant.

Sizing Management Server

Gateway to Management Node ratio should be:
  • 3 Gateways per Management Node for virtual GWs with 2 vCPUs or 4vCPUs
  • 2 Gateways per Management Node for virtual GWs with 8vCPUs
  • 1 Gateway per Management Node for virtual GWs with 12vCPU or more and all physical Gateways
Analytics heap size (since v4020) :
  • Allocated as 1GB on Management Nodes with <16GB memory
  • Allocated as 8GB on Management Nodes with 16GB or more memory. This is now recommended for production systems with moderate to heavy loads
Disk space is calculated using the following multiplication:
  • Average # of api calls per day *720 bytes per api * Average size of headers {If header or payload logging active}*Average size of payload {If payload logging active}*90 days *0.60 compression ratio
User-added imageSizing Advanced Developer Portal

The primary factors involved in a developer portal sizing are:

  • Number of sites
  • Number of concurrent users
hardware requirements

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSQTW3","label":"IBM On Demand Consulting for Hybrid Cloud"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
17 February 2022

UID

ibm10773009

Page Feedback