You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In versions v41.2.0 to v44.0.0, you may encounter performance regressions when using the SDK with some OCI services. This performance regression has been fixed in versions 45.0.0 and later.
The regression surfaces itself as a 3 seconds increase in latency in SDK operations made to some OCI services. This issue has been confirmed to impact the OCI Streaming service, and likely impacts the Email Delivery, Health Checks, NoSQL Database Cloud, Registry, Generic Artifacts, and Web Application Acceleration and Security services as well. This list is not comprehensive – it is possible you may encounter the issue against other OCI services as well. The issue has been confirmed to NOT affect the OCI Object Storage service.
If you are experiencing this issue there are some workarounds you can do:
Recommended: Disable support for the SDK's Expect 100-Continue feature by setting environment variable export OCI_GOSDK_USING_EXPECT_HEADER=FALSE
Or, use SDK version v41.1.0 or earlier
Or, use the SDK's raw request signer to make requests to OCI services for any requests where you are experiencing performance degradation. An example of how to use the raw request signer is here Raw Request Signer Example
If you have any questions, please feel free to comment on this GitHub issue and we will be happy to help.
The text was updated successfully, but these errors were encountered:
In version v45.0.0 and later, the performance regression has been fixed.
jodoglevy
changed the title
Performance regression in the Go SDK
Performance regression in versions 41.2.0 to 44.0.0 for some services (fixed in v45.0.0)
Jul 21, 2021
In versions v41.2.0 to v44.0.0, you may encounter performance regressions when using the SDK with some OCI services. This performance regression has been fixed in versions 45.0.0 and later.
The regression surfaces itself as a 3 seconds increase in latency in SDK operations made to some OCI services. This issue has been confirmed to impact the OCI Streaming service, and likely impacts the Email Delivery, Health Checks, NoSQL Database Cloud, Registry, Generic Artifacts, and Web Application Acceleration and Security services as well. This list is not comprehensive – it is possible you may encounter the issue against other OCI services as well. The issue has been confirmed to NOT affect the OCI Object Storage service.
If you are experiencing this issue there are some workarounds you can do:
export OCI_GOSDK_USING_EXPECT_HEADER=FALSE
If you have any questions, please feel free to comment on this GitHub issue and we will be happy to help.
The text was updated successfully, but these errors were encountered: