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
I documented in golang/go#71414 how go1.23 has changed the behavior of the go run and go install commands such that each invocation calls the list API, which is not cached by athens. This has caused us to hit S3 ListObjectsv2 rate limits, regardless of whether we use general purpose or directory buckets. To mitigate this, we cache the results of the list API for 60s with a frontend cache, even though athens serves a very strict cache-control header precluding this. proxy.golang.org does the same thing.
This is mostly an FYI in case other service owners are seeing increasing error rates as go 1.23 is adopted.
The text was updated successfully, but these errors were encountered:
I documented in golang/go#71414 how go1.23 has changed the behavior of the
go run
andgo install
commands such that each invocation calls thelist
API, which is not cached by athens. This has caused us to hit S3 ListObjectsv2 rate limits, regardless of whether we use general purpose or directory buckets. To mitigate this, we cache the results of the list API for 60s with a frontend cache, even though athens serves a very strict cache-control header precluding this. proxy.golang.org does the same thing.This is mostly an FYI in case other service owners are seeing increasing error rates as go 1.23 is adopted.
The text was updated successfully, but these errors were encountered: