App startup lag around linkDynamicModule

[zackarychapple]

Using RC0 and the AngularCLI I have generated a project and after working on it for a while I performed a prod build in the CLI and tested the deploy of the project. I noticed there is an almost 1 second delay from the point at which my main.js and index.js files are retrieved and my first component is pulled down.

Here is my bootstrap.
bootstrap(WfaNg2AppComponent, [ ROUTER_PROVIDERS, provide(LocationStrategy, { useClass: HashLocationStrategy }) ]);

Here is the network tab during the bootstrap.

Here is the timeline for that period of wait.

If I turn off hash location strategy here is my network.

Here is the timeline with the hash location strategy off.

[sod]

Module loader performance in general is very disappointing if you throw the angular modular structure against it. I guess thats the reason why the bundles where removed in rc.0

At the moment the team experiments with http://rollupjs.org/. A module bundler that can get rid of the module syntax alltogether and removes unused methods in the process.

@robwormald has a test repository https://github.com/robwormald/ng2-compiler-test2 that spawned from ng-conf. The build there is just 50kb gzipped and loads very fast. I hope he writes a blog about it or we get a rollup guide like the webpack one on https://angular.io/docs/ts/latest/guide/webpack.html

[zackarychapple]

Thats good information, I remember that talk well, the performance was fantastic. I use the CLI though so I'm not quite ready to change the build strategy just yet.

[IgorMinar]

the AOT compilation and squashing modules via rollup addresses this problem. CLI will have these features enabled by default in the future releases. In the meantime it's possible to set these up via your own build pipeline.

[zackarychapple]

@IgorMinar looks like it's in the current build 1.0.0-beta.16 of the CLI. angular/angular-cli#1732 (comment) Thank you again for helping to make sure this got fixed.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}