feat: (simple) load test one-by-one bulk upload#6416
Draft
emilyjablonski wants to merge 3 commits into
Draft
Conversation
emilyjablonski
changed the title
✅ Deploy Preview for partners-bloom-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for bloom-angelopolis canceled.
|
✅ Deploy Preview for bloom-public-seeds ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for bloom-exygy-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Option 1 (transaction) - 1000 records
Option 2 (one-by-one) - 1000 records
Option 1 is ~19% faster, but almost entirely due to the bulk read. Snapshot cost is the same either way.
The speed difference is real but somewhat small - it seems like Option 1 saves about 40 seconds on a job that takes 5-6 minutes without emails.
The only thing you gain with Option 1 is one fewer round-trip per record on the read side. The theoretical harder part - snapshots - is identical. It appears to be saving about 40 seconds on an estimated total 30-40 minute job.
Email sends remain the dominant variable - at ~200ms/email, 50% of records triggering notifications adds ~17 min regardless of which option is used.