Boto3 Performance degradation after ugprade from python 3.8 to 3.12

[jricardooliveira]

Describe the bug

We have been experiencing significant performance degradation in our services after upgrading our environment from Python 3.8 with boto3 1.28 (container running python:3.8.16-slim-buster) to Python 3.12 with any version of boto3 greater than or equal to 1.28 (container running python:3.12.2-slim-bookworm).

Expected Behavior

The performance should be consistent across requests, similar to the behavior observed in the Python 3.8 environment.

Current Behavior

Reproduction Steps

1- Set up a container with Python 3.8.16-slim-buster and boto3 1.28. 2 - Set up a container with Python 3.12.2-slim-bookworm and boto3 1.28 or higher. 3 - Send multiple burst requests from a single user to a service using boto3.

In the screenshot you may see the performance degradation before and after and the culprit... boto3 kinesis POST request.

Possible Solution

No response

Additional Information/Context

We suspect that the connection initialization process in the newer environment might be causing this issue. Any insights or suggestions on how to address this performance degradation would be greatly appreciated.

SDK version used

1.28.x 1.34.x

Environment details (OS name and version, etc.)

Container Debian slim-bookworm