Performance regression in versions 2.14.1 and later for all API operations

Update : We have fixed this issue in version 2.66.2 and 3.31.0 of the SDK by using an idle connection monitor. More details can be found here

In versions 2.14.1 and later, you may encounter performance regressions when using the SDK to call API operations to any of the OCI services. The regression ranges from 30% to 60% increase in latency in SDK operations to any of the OCI services.

If you are experiencing this issue, and would like to get the older performance back, there are some workarounds you can do:

• Switch back to the Jersey’s default HttpUrlConnectorProvider by setting the OCI_JAVASDK_JERSEY_CLIENT_DEFAULT_CONNECTOR_ENABLED environment variable to true or any other methods mentioned here
• Disable the use of NoConnectionReuseStrategy for the ApacheConnectorProvider by setting the ApacheConnectorProperties.connectionReuseStrategy to null and ApacheConnectorProperties.requestRetryHandler to null

// For clients that should not buffer requests into memory
ObjectStorageClient client = ObjectStorageClient.builder().clientConfigurator(new ApacheConfigurator.NonBuffering(
        ApacheConnectorProperties.builder().
                .connectionReuseStrategy(null)
                .requestRetryHandler(null)
                .build()
)).build(provider);

// For clients that should buffer requests into memory
IdentityClient identityClient = IdentityClient.builder().clientConfigurator(new ApacheConfigurator(
        ApacheConnectorProperties.builder()
                .connectionReuseStrategy(null)
                .requestRetryHandler(null)
                .build()
)).build(provider);

• Or, use SDK version 2.14.0 or earlier.

If you have any questions, please feel free to comment on this GitHub issue and we will be happy to help.

The issue points to ApacheConnector-README.md and the ApacheConfigurator and ApacheConnectorProperties entry points. Start by reviewing the documented idle connection monitor fix and affected SDK versions; done is not defined because the regression is reported fixed in versions 2.66.2 and 3.31.0.