Skip to Main Content
HCL Domino Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Status Under Consideration
Created by Guest
Created on Oct 30, 2020

HEI should issue multiple row updates in one connection to improve latency

When all servers (Domino, HEI & SQL) are either on the On-Premise or on the AWS instance, then there is good latency seen while doing SQL based activities. However, when Domino & HEI are on the AWS instance and the SQL server is on the On-Premise then poor latency is seen while doing same SQL based activities.

The network throughput between HEI and SQL server isn't an issue, however there seems to be a lot of latency. The trace file for the data received by the SQL server shows HEI is issuing individual row updates establishing a connection for each update. This will impact the network performance of a connection with poor latency.

Increasing the 'Number of Records to Transfer Concurrently' value for the Connection document in HEI had very limited effect and was not useful to improve latency.

Expectation :

HEI should issue multiple row updates in one connection to improve latency .

  • Attach files