Skip to content
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

general output time and modules with no loaders #59

Open
daton89 opened this issue Nov 8, 2018 · 6 comments
Open

general output time and modules with no loaders #59

daton89 opened this issue Nov 8, 2018 · 6 comments

Comments

@daton89
Copy link

daton89 commented Nov 8, 2018

during start i can see that modules with no loaders is the most expensive part but i have no more detail about that, which are the modules without loader?:

 SMP  ⏱
General output time took 31.27 secs

 SMP  ⏱  Plugins
Object took 0.016 secs
ProvidePlugin took 0.001 secs

 SMP  ⏱  Loaders
modules with no loaders took 15.96 secs
  module count = 6838
babel-loader took 4.42 secs
  module count = 107
css-loader took 2.26 secs
  module count = 16
underscore-template-loader took 1.11 secs
  module count = 24
json-loader took 0.636 secs
  module count = 2
file-loader took 0.151 secs
  module count = 11
style-loader, and
css-loader took 0.012 secs
  module count = 5

during reload my worst loading time comes from general output time:


 SMP  ⏱
General output time took 6.079 secs

 SMP  ⏱  Plugins
Object took 0.005 secs
ProvidePlugin took 0 secs

 SMP  ⏱  Loaders
babel-loader took 0.294 secs
  module count = 1

what does it mean? is it the time spent to compile my own code? how can i figure out the optimization for this?

@daton89 daton89 changed the title general output time general output time and modules with no loaders Nov 8, 2018
@zk2401
Copy link

zk2401 commented Dec 20, 2018

same question

@katherinebernstein
Copy link

+1

@stephencookdev
Copy link
Owner

Hey 😄 Sorry for the very late response

"modules without loaders" basically just means vanilla JS files, which webpack can handle out of the box.

As for the "general output time" on the reload, this tends to be generally down to webpack reading in from the file-system, but it's hard to say - it'll be very repo specific!

Where would you all look for information on this? Would a link to a README doc or something, just under the "modules with no loaders" description?

@dutzi
Copy link

dutzi commented Sep 10, 2019

@daton89 Try playing with the devtool property, set it eval to see if you see any significant change, if so read Webpack's docs and try the other, less cheap, options

ThomasHarper added a commit to ThomasHarper/speed-measure-webpack-plugin that referenced this issue Mar 7, 2020
I found myself having the same questions as in this [issue](stephencookdev#59).
Seems there was no answer from the issue opener so I'd like to have this in the readme.

The answer for the "general output time" is still pretty unclear for me and I'd love more feedback on this matter from you @stephencookdev 

Cheers,
@IanVS
Copy link

IanVS commented Jul 14, 2020

Looks like this has been answered in the Readme, and can probably be closed?

@akoushke
Copy link

@daton89 Try playing with the devtool property, set it eval to see if you see any significant change, if so read Webpack's docs and try the other, less cheap, options

this is insane!!! this made a significant change! but why?? 💯

sunft1996 pushed a commit to sunft1996/speed-measure-webpack-plugin-source-read that referenced this issue Jul 20, 2023
I found myself having the same questions as in this [issue](stephencookdev#59).
Seems there was no answer from the issue opener so I'd like to have this in the readme.

The answer for the "general output time" is still pretty unclear for me and I'd love more feedback on this matter from you @stephencookdev 

Cheers,
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants