-
Notifications
You must be signed in to change notification settings - Fork 55
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
CCDM: v15 webpack build is slower than v14 #331
Comments
Haijian will talk to the Flow team to see if we can close the ticket. |
Since the test actually does not check real project stuff, we need to verify whether the design of the bootstrap process in v15 is good.
Update: we have done some time and size measurements: https://docs.google.com/spreadsheets/d/12dl-QLUzgMOtUYVjun9XRB1X1DqUqKVgPpFSbA4I2yQ/edit#gid=0 |
Unmute StartupPerformanceIT.devModeInitializerToWebpackUpIsBelow5500ms at https://teamcity.vaadin.com/viewType.html?buildTypeId=Flow_FlowTests&branch_Flow=7737&tab=buildTypeStatusDiv when done |
Apparently one reason why 15+ is slower than 14 is the |
See
StartupPerformanceIT.devModeInitializerToWebpackUpIsBelow5500ms
, the threshold should be set to 5500 but in v15 it needs to be 9500 to passConsiderations:
target/frontend/generated-flow-imports.js
only importing the@vaadin/flow-frontend/dndConnector-es6.js
, in consecuence webpack in does not visit, bundle and optimize complex dependenciesfrontend/index.ts
which includesRouter
,Flow
andConnect
having to optimize a big amount of code. In a fast system it takes about 3000ms extra.BootstrapHandler.js
andclient-nnnnn.cache.js
files in order to include them in the bundle.Probably this increment of the build time is assumable, because browser does not need extra requests for getting the
client-cache
code.The text was updated successfully, but these errors were encountered: