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

High cpu on docker container due to webpack analyzer #153

Closed
diiaann opened this issue Feb 19, 2018 · 4 comments
Closed

High cpu on docker container due to webpack analyzer #153

diiaann opened this issue Feb 19, 2018 · 4 comments

Comments

@diiaann
Copy link

diiaann commented Feb 19, 2018

Issue description

In between 2.9.1 and 2.10.1 we noticed that upon starting our webpack build, our rebuilds were extremely slow. After the initial webpack build command, cpu usage would shoot up to >99% and stay there. Thus subsequent rebuilds due to the watch command would take minutes instead of the usual second. Holding everything constant and pinning the version of webpack-bundle-analyzer to 2.9.1 caused the issue to go away.

Technical info

  • Webpack Bundle Analyzer version:
    2.10.1
  • Webpack version:
    3.11.0
  • Node.js version:
    v6.12.0
  • npm/yarn version:
    3.10.10
  • OS:
    Docker for Mac on MacOS Sierra , with this container
Distributor ID:	Ubuntu
Description:	Ubuntu 14.04.4 LTS
Release:	14.04

Debug info

How do you use this module? As CLI utility or as plugin?

Plugin

If plugin, what options were provided? (e.g. new BundleAnalyzerPlugin({ analyzerMode: 'disabled', generateStatsFile: true }))

      new BundleAnalyzerPlugin({
        analyzerMode: 'static',
        analyzerPort: 8888,
        reportFilename: 'webpackReport.html',
        openAnalyzer: false,
        generateStatsFile: true,
        statsFilename: 'stats.json',
      })
@valscion
Copy link
Member

Hi! Thanks for the detailed issue, I'll look into it.

When you say "version 2.10.1", you probably mean 2.10.0, right? I don't think we've published a patch release after 2.10.0 ☺️

@valscion
Copy link
Member

Could you try running with generateStatsFile: false? It's likely that your high CPU usage is due to #129. Could you verify that version 2.9.2 still works for you, so that we can be sure the regression happened between 2.9.2 and 2.10.0?

@valscion
Copy link
Member

Hi @diiaann, have you had a chance to look into my earlier comment? ☝️

@th0r
Copy link
Collaborator

th0r commented Apr 11, 2019

Closed due to inactivity.

@th0r th0r closed this as completed Apr 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants