-
Notifications
You must be signed in to change notification settings - Fork 512
Horrible webpack performance (8x) when ExtractTextPlugin is present #144
Comments
Same issue here. (actually worse, 13x in my case) |
Have you guys always had this performance issue or is it with specific releases of the plugin? |
I have tried with 0.8.2 and 1.0.0 and I have the issue on both versions |
@alberto do you have any idea why? |
No. I updated some package dependencies, and tweaked the configuration and the problem went away, but I don't know what was causing it. |
Would you be so kind to provide me with your configuration? so I can compare with mine. |
My config is a bit complex. Let me try to figure out what was it. |
Try updating your loaders. One of this fixed it for me:
|
it still very slow to me. |
Sorry, here is my config in case it helps: https://gist.github.com/alberto/c273f2623e13c256bacb |
I have the same problem as well. |
I believe this plugin is considerably slowing down my webpack builds as well. Are there any solutions to this? |
same issue here |
Can you try against webpack 2? |
Still slow here. Not 100% sure if it is because of ExtractTextPlugin or not but 99% sure. Using css imports in 20+ files so I cannot easily test it by removing it because it would break my whole webpack build 😕 but I'm using a very similar webpack config without ExtractTextLoader in another project of similar size and complexity and build times are around 3-5 times faster there. Webpack develop build takes 13.027s on my machine and this is my config:
Webpack version is 2.2.0. Maybe postcss-loader or sass-loader are the cause. I dont know 😕 |
By simply setting |
im also getting really slow builds with extract text plugin - if i set |
I ran into this problem as well. I tracked it down to webpack-contrib/css-loader#124, using css-loader 0.14.5 dropped my build time by 30%. |
@KazW that may well be a part of the issue, but if I only disable extract text plugin, and keep css-loader+sass-loader, it literally halves my build time. It seems clear that extract text plugin itself is a huge source of slowness |
Seems issue related to /cc @matthewjumpsoffbuildings @GuilhermeMedeiros @manuelbieh @Hulkmaster @allenylzhou @alberto The problem is still present? If yes, please provide minimal reproducible test repo. |
@evilebottnawi not in my experience - if i disable extract-text-webpack-plugin and leave css-loader and sass-loader enabled, my compile time halves. it appears to have something to do with extract-text-webpack-plugin and sass includes. it seemed like the more sass includes i used (both from my own files and from npm sass libraries like susy and bourbon), the more the compile time increased. i will attempt to make a test repo asap |
@matthewjumpsoffbuildings just ping me when your do it |
@matthewjumpsoffbuildings getting the same thing. extract-text-webpack-plugin is getting worse at a exponential rate, it is not scaling. |
In essence extract-text is a hack to make up for a lack of first class css support in Webpack. Trying to Step 1 of a few on the road to solving the performance issues in the CSS workflow the right way. Everyone is going to have to bear with us while we get this handled, it's an Information related to this topic is pushed out publicly on medium.com, the best way to stay current would be to follow https://medium.com/webpack && https://medium.com/@sokra. You will in most cases, end up with detailed information the same time as myself, @michael-ciniawsky, @bebraw & @evilebottnawi get it. |
I've tried many things already, and I can't get rid of the performance issues when using the ExtractTextPlugin.
This is my stats.json file WITH ExtractTextPlugin
stats.json.zip
And the configuration looks something like:
and my stats WITHOUT ExtractTextPlugin
stats.json.zip
where
Because I'm generating two bundles, the performance is twice as bad.
I really don't know what to do.
The text was updated successfully, but these errors were encountered: