Performance Difference Observed Between IIB and SAP IS – Database Query Response Time

[#1]

Hello Experts,

I am an IBM Integration Bus (IIB) resource currently working on a migration project where I’m assisting the SAP Integration team by providing the IIB landscape and architecture required for migration to SAP Integration Suite (SAP IS).

As part of a small performance comparison and feasibility test, I simulated a very basic database interaction scenario in SAP IS and observed a significant difference in response time compared to IIB.  I would appreciate guidance on whether this is expected behavior or caused by trial environmental limits.
[Note]:I also tried interacting with IBM MQ SAAS and compared SAP IS and IBM IIB results, again, ending with similar situation(not covered in this Post).

Test setup and observations:

• I created a SAP HANA Cloud (trial) database for testing.
• Added a single test table containing only 3 rows of static data.
• Built a simple SAP iFlow with:
  • An HTTP Sender Adapter to invoke the flow.
  • Three simple SELECT statements(3 calls) to the HANA DB (no transforms, no mappings).
  • No other processing steps.
• When I invoke the iFlow via HTTP, the total response time is around 7–10 seconds consistently.
• For comparison, I implemented the same logic in IIB (connected to an SQL Server) and observed typical response times of 100–200 ms. (Occasionally the first call after a long idle takes ~500–700 ms.)

Additional context:

• The SAP IS trial account is hosted in the US East (VA)-AWS region, whereas the SAP HANA Cloud trial database is in the Singapore Azure region.
• In the IIB scenario, both IIB runtime and the SQL Server database are co-located in the same data center, likely explaining the ultra-low latency observed there.
• The http request is initiated(for both tests) using postman from Cloud PC somewhere in US.
• I understand that cross-region latency can contribute to higher response times, but a difference of 7–10 seconds vs 100–200 miliseconds still feels unusually high for such a lightweight query.

Primary question:

Is the observed delay in SAP IS due to the HANA Cloud trial environment (resource throttling, cold starts, or connection setup time on every request sent), or is there inherent overhead in SAP IS runtime for such DB interactions?

Specific areas where guidance would help:

• Does SAP IS / DB adapter use connection pooling or persistent connections to the database?
• Are there known limitations in trial HANA or IS tenants that can cause high round-trip time?
• Are there runtime or adapter-level settings to minimize latency for repeated database operations?
• Would response time improve noticeably in a production-grade tenant (same region) setup?

I would greatly appreciate any insights, documentation references, or configuration tips to help understand and potentially improve this response time behavior.

-Dhruv