class AuthBoto performance issue
- Dominant language
- Python
- Stars
- 26
- Forks
- 19
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 1
Description
In the current implementation, AuthBoto recreates the boto3.Session() for every mlflow.log_metric() call. This significantly slows down the program when there are multiple log_metric() calls. I think the AuthBoto class should be able to cache the credentials for a period of time, or reuse the credentials until they're about to timeout. This can significantly improve performance.
Contributor guide
Research direction
Start by locating the AuthBoto class and the boto3.Session() creation used during mlflow.log_metric() calls. Trace how credentials are obtained and expire, then identify existing tests covering AuthBoto or metric logging. Done means repeated logging avoids unnecessary session creation while still refreshing credentials safely before timeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- authentication, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100