-
Notifications
You must be signed in to change notification settings - Fork 4k
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
(assets): publish Assets in parallel #19193
Comments
In my project, I observed these timings: 11 assets (10 functions): 3 assets (10 functions): In aggregate, all assets are under 28MB. |
I was fiddling with a toy implementation. Here's a hot-swap comparison for 60 assets and 60 lambda functions: Sequential (57 seconds) Parallel Asset Publishing (18 seconds) |
Sequential (57 seconds) publish-sequential.mp4
Parallel Asset Publishing (18 seconds) publish-parallel.mp4cc @misterjoshua :) |
Adds parallel asset publishing. In a 60-asset/60-Lambda test project, this change decreases the total hot-swap time from 57 seconds to 18 seconds. Fixes #19193 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
Description
Right now, we publish the Assets serially. This is slow if the customer's App contains many Assets (it's visible with as little Assets as 10).
Use Case
CDK Apps with many (10+) Assets.
Proposed Solution
We should switch to publishing the Assets in parallel, instead of serially. The tricky part of this will be making sure the Asset publishing progress messages are handled correctly.
Other information
No response
Acknowledge
The text was updated successfully, but these errors were encountered: