perf(drizzle): update collection related tables in parallel #14868
+287
−244
Conversation
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
rjgtav
force-pushed
the
rjgtav/perf-drizzle-upsertrow-parallel
branch
from
ac03c0d to
da07846
Compare
AlessioGr
reviewed
Dec 9, 2025
Member
There was a problem hiding this comment.
We should do the same with insertArrays
Contributor
Author
There was a problem hiding this comment.
Hi @AlessioGr ! Just submitted a new commit which goes further in parallelizing the different steps. Is this what you were thinking about?
rjgtav
force-pushed
the
rjgtav/perf-drizzle-upsertrow-parallel
branch
from
5753f1f to
f54cc04
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What?
Updates upsertRow.ts to run the deletes/inserts for related tables in parallel.
Why?
To optimize the total request time when creating/updating new entries on collections with relationships and other advanced fields (e.g. number field with hasMany, text field with hasMany, locales). Particularly impactful when the database is further away from the Payload instance.
How?
By collecting the delete/insert operations and running all of them at the end.