-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
perf: send seed data requests asynchronously #2825
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure on other machines, but locally I'm actually getting slower results.
Async: 10:09:11 - 10:12:45 = 3 minutes 34 seconds
Sync: 10:16:11 - 10:19:36 = 3 minutes 25 seconds
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Async ran for me in 5:17 while sync was 6:10.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so almost a minute improvement, not great, not awful
Should we go ahead and merge? or any concerns about adding the async-ness in general?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks good to me! I was testing around with lower memory / cpu and got similar results to Mary's!
PULL REQUEST
Summary
Use asynchronous requests when converting seed data. Locally, this speeds up conversion from 8:45 to 5:12
create-seed-data-py
script into two phases: 1) gathering all the requests to send, 2) sending all the requests async and handling responsesn of total
printing, which I find a nicer ux