performance question

[babsonmatt]

Tried out devtool and iron-node, the start up times seem to be quite different for my app:

devtool: 4.7s iron-node 1.7s

Any ideas what might be leading to this or if this is something that might be improved upon in future versions of devtool?

Thanks a lot!

[mattdesl]

It should be something that we can iterate/improve on. The main difference is that devtool waits for domready events, but I'm not sure that explains the huge difference.

Is there any way I can test/reproduce the issue? I haven't noticed such long times here. Also what node/npm/system specs are you testing with? And how are you measuring the time?

Thanks!

Sent from my iPhone

On Jan 26, 2016, at 2:38 AM, Matt [email protected] wrote:

Tried out devtool and iron-node, the start up times seem to be quite different for my app:

devtool: 4.7s iron-node 1.7s

Any ideas what might be leading to this or if this is something that might be improved upon in future versions of devtool?

Thanks a lot!

— Reply to this email directly or view it on GitHub.

[babsonmatt]

Hey sorry for the delay in getting back to you!

The project uses babel which makes up most of the loading time, although I'm not sure what iron-node must not being doing that devtool is (to account for the difference in load time).

The results I posted above were on a 2015 macbook pro with node 5.5 / npm 3

Thanks!