Provide more insight into botocore startup time

[tim-finnigan]

Is your feature request related to a problem? Please describe. Consolidating https://github.com/aws/aws-cli/issues/6500 and https://github.com/boto/boto3/issues/3061 here, as botocore provides the core functionality for both the CLI and boto3.

Describe the solution you'd like Documentation or guidance giving more insight into the core botocore processes. Specifically to provide more understanding of how long the typical startup time takes and which parts could potentially be optimized.

---

As a general point users should be sure to update to the latest versions of the AWS CLI and boto3.

To get more insight into runtimes for the CLI you can see the debug logs by adding --debug to any command, and for boto3 you can get a full stack trace by adding boto3.set_stream_logger('') to your script.

It's also worth nothing that users will experience a wide range of times depending on the services, commands, and hardware used.

Generally speaking the startup process involves starting a Python interpreter and then making various imports. The next bottleneck is usually reading a model file, which in the case of services such as S3 could be somewhat large.

[tim-finnigan]

Also worth mentioning this recent feature request to compress schemas: https://github.com/boto/botocore/issues/2365

[github-actions[bot]]

Greetings! It looks like this issue hasn’t been active in longer than one year. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.