sentry-cli: Slow sourcemap upload
I’m having issues with the upload time to sentry.io.
Our sourcemaps are ~30mb, and it takes over 5 minutes to upload them. As we do this as part of CI it slows our build times down.
Unlike https://github.com/getsentry/sentry-cli/issues/17 the upload is consistently slow.
The upload is happening from our corporate network (very fast internet), so it seems unlikely it is related to our connection. (e.g. uploading the same sourcemaps to other cloud providers takes just seconds)
Our build script calls this (after first verifying if a release exists, and creating one if not):
sentry-cli releases -p OUR_PROJECT files OUR_REVISION upload-sourcemaps ./path/to/built/code
There is a ~/.sentryclirc which specifies some defaults (our org, auth token, log level etc)
Can anyone suggest ways to speed this up / further investigate why it’s slow?
I’ve run the upload with log level trace but didn’t see anything illuminating in the log.
EDIT: one thing I just noticed is for some files it first requests a DELETE for that file before doing the POST. I’m not sure why it would do this as I’m creating a new release each time before uploading, so there should be no existing files associated with the release.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 8
- Comments: 23 (9 by maintainers)
@jan-auer any updates? This is causing intermittent flakiness in our CI/CD process. Are there any suggested workarounds? Anything I can do to help debug this more?
Hello,
Any update on this ? Source upload is now 20% of our build time 😦
As noticed in now-closed #405 probably the main reason of slow upload isn’t lack of compression, but rather uploading of tenths or hundreds of files separately instead archiving them and uploading as one. I hope this issue will be closed only when both improvements are applied or #405 is reopened.
This has been resolved as of
sentry-cli v1.44.0. It requires sentry.io, or for on-premise a recent installation ofmaster. The Sentry 10 release will also include the server-side changes.We are also loosing a lot of time because of that. Is there any update? As stated in #405 there is a fix planned and on the roadmap. Would you mind sharing a timeline?
Any update here? It’s taking a major chunk of deployment time.